Synopsis

Moderate: Red Hat Certificate System 8 security, bug fix, and enhancement update

Type/Severity

Security Advisory: Moderate

Topic

An update is now available for Red Hat Certificate System 8 with Advanced Access.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Description

Red Hat Certificate System is a complete implementation of an enterprise software system designed to manage enterprise public key infrastructure (PKI) deployments.

Security Fix(es):

• An input validation error was found in Red Hat Certificate System's handling of client provided certificates. If the certreq field is not present in a certificate an assertion error is triggered causing a denial of service. (CVE-2017-7509)
  

Bug Fix(es):

• Previously, the Token Management System (TMS) required that certificates that were on hold must first become valid before they can be revoked. This update removes that limitation, and it is now possible to directly revoke currently on hold certificates. (BZ#1262000)
  
• With this update, Red Hat Certificate System instances can be installed using existing CA signing certificate/keys. This existing CA can be a functional CA from a different vendor, or keys or CSR generated to be signed by an external CA for the purpose of chaining it to a publicly recognized CA.
  

Note that this feature is only supported when installing with the "pkisilent" tool, not when using the graphical user interface. Additionally, since the CSR is generated externally prior to configuration of the CA instance and is not stored in the NSS security databases, it should be understood that the CSR value attached to the "ca.signing.certreq" variable stored inside the "/var/lib/pki-ca/conf/CS.cfg" file is a reconstruction of the CSR created during configuration, and not the original CSR utilized to obtain the existing CA certificate. (BZ#1280391)

• Previously, a bug in CRLDistributionPointsExtension caused some certificate profiles to encounter problems when being viewed in the Certificate Manager graphical interface. This bug is now fixed, and aforementioned profile can now be viewed normally. (BZ#1282589)
  
• Previously, if access to a component such as an HSM or an LDAP server was lost during Certificate Revocation List (CRL) generation, the CA could become stuck in a loop that generated large amounts of log entries until the problem was resolved. To avoid these scenarios, two new configuration parameters are being introduced in this patch to allow the CA to slow down. (BZ#1290650)
  
• A patch has been applied to the Token Processing System (TPS) to ensure that the "symmetricKeys.requiredVersion" option is being handled correctly in all cases. (BZ#1302103)
  
• A patch has been applied to the Certificate System Token Processing System (TPS) to fix a bug where existing objects were not always cleared when enrolling over an active token. (BZ#1302116)
  
• This update fixes a bug where the Token Processing System (TPS) could not correctly execute re-enrollment operations (taking a currently enrolled token and enrolling it again with new certificates) on some G&D smart cards. (BZ#1320283)
  
• The Token Processing System (TPS) could previously leave old data in a token's Coolkey applet when re-enrolling the token with new certificates and keys. This bug is now fixed, and only data associated with certificates which are actually on the token is preserved after a successful re-enrollment. (BZ#1327653)
  
• Previously, a problem when setting the final life cycle state of a token at the end of a re-enrollment operation could cause it to fail to report that it is properly enrolled. This bug is now fixed, and re-enrolled token now report their "enrolled" status accurately. (BZ#1382376)
  
• Prior to this update, ECDSA certificates were issued with a NULL value in the "parameter" field. These certificates were not compliant with the RFC 5758 specification which mandates this field to be omitted completely. This bug has been fixed, and ECDSA certificates are now issued without the "parameter" field. (BZ#1454414)

Solution

For details on how to apply this update, which includes the changes described in this advisory, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Certificate System with Advanced Access 8 x86_64
• Red Hat Certificate System with Advanced Access 8 i386

Fixes

• BZ - 1456030 - CVE-2017-7509 certificate system 8: Enrolling certificate without certreq field causes CA to crash

CVEs

• CVE-2017-7509

References

• https://access.redhat.com/security/updates/classification/#moderate

Red Hat Certificate System with Advanced Access 8

SRPM
pki-ca-8.1.9-2.el5pki.src.rpm	SHA-256: ce96667e7692b794c87394db29d5c38e35f985fe5f4ca676e311898670598550
pki-common-8.1.20-1.el5pki.src.rpm	SHA-256: edde710bf2a4fbdb0cbcc9cf0a4c25bb573c9c913ccc4c635585072e35c72309
pki-kra-8.1.7-2.el5pki.src.rpm	SHA-256: e3093ba63327694a0571464190e5ae1b1ec544661d00c2c24084907333e2abc4
pki-silent-8.1.2-3.el5pki.src.rpm	SHA-256: 21670cef71b9d7f36937ad2bbeae33c743c4faa22455f8f5f26a7f05d271ead2
pki-tps-8.1.30-1.el5pki.src.rpm	SHA-256: 3343770c462943cd988f84b2b13a421d54334a6688089583754308785f769205
pki-util-8.1.3-2.el5pki.src.rpm	SHA-256: 85831a8ff705077a8f45766df7ca613413e134fc2ee8b5e5a744a6e6542b339c
redhat-pki-ca-ui-8.1.1-2.el5pki.src.rpm	SHA-256: 271204af0159da3ef7ea9ffc4bd3249840169e9054696caa73d2325d58e16dee
x86_64
pki-ca-8.1.9-2.el5pki.noarch.rpm	SHA-256: 092e9a2b6b3edf0ffc1d914c763754bbfc1b12365d315871dc8d281ca355808a
pki-common-8.1.20-1.el5pki.noarch.rpm	SHA-256: 98b59cb2c879d829ea4d05f273e27a90528b225555858acf1e39686fa2bbdb2e
pki-common-javadoc-8.1.20-1.el5pki.noarch.rpm	SHA-256: 154b5ef68718f3989d6994ae8d74ee9d62c31d45cec590a7505c77c3e2e759a2
pki-kra-8.1.7-2.el5pki.noarch.rpm	SHA-256: 3557d62e32257f14bb9f2c1379984b8418c97ceda70d70e6c1508c824c6ddc42
pki-silent-8.1.2-3.el5pki.noarch.rpm	SHA-256: 64243f0b165dbaf614bc43f8621644472cae4a297775e0872b61ddbbd10d2955
pki-tps-8.1.30-1.el5pki.x86_64.rpm	SHA-256: 8c3d75c00ecf2df0e962af992130852c1551d01a464c7d10d8059eeddcbf95d6
pki-util-8.1.3-2.el5pki.noarch.rpm	SHA-256: 130022d0f0debd5ad02ff8387a5694a199cb385a7a312269ab2a98e074c40298
pki-util-javadoc-8.1.3-2.el5pki.noarch.rpm	SHA-256: 4aa19d8322bd8c4324f02b10730bc1c513e1121a06c7d8cd67ab6141e954dfb3
redhat-pki-ca-ui-8.1.1-2.el5pki.noarch.rpm	SHA-256: cb70759964dfb1204253056ee251309745cfe72af597ecc4a28fb5f595679e58
i386
pki-ca-8.1.9-2.el5pki.noarch.rpm	SHA-256: 092e9a2b6b3edf0ffc1d914c763754bbfc1b12365d315871dc8d281ca355808a
pki-common-8.1.20-1.el5pki.noarch.rpm	SHA-256: 98b59cb2c879d829ea4d05f273e27a90528b225555858acf1e39686fa2bbdb2e
pki-common-javadoc-8.1.20-1.el5pki.noarch.rpm	SHA-256: 154b5ef68718f3989d6994ae8d74ee9d62c31d45cec590a7505c77c3e2e759a2
pki-kra-8.1.7-2.el5pki.noarch.rpm	SHA-256: 3557d62e32257f14bb9f2c1379984b8418c97ceda70d70e6c1508c824c6ddc42
pki-silent-8.1.2-3.el5pki.noarch.rpm	SHA-256: 64243f0b165dbaf614bc43f8621644472cae4a297775e0872b61ddbbd10d2955
pki-tps-8.1.30-1.el5pki.i386.rpm	SHA-256: a6cb6ae7978d126504036c81feb24d73655a3b9ceaf11a285ed466d38c4fc60f
pki-util-8.1.3-2.el5pki.noarch.rpm	SHA-256: 130022d0f0debd5ad02ff8387a5694a199cb385a7a312269ab2a98e074c40298
pki-util-javadoc-8.1.3-2.el5pki.noarch.rpm	SHA-256: 4aa19d8322bd8c4324f02b10730bc1c513e1121a06c7d8cd67ab6141e954dfb3
redhat-pki-ca-ui-8.1.1-2.el5pki.noarch.rpm	SHA-256: cb70759964dfb1204253056ee251309745cfe72af597ecc4a28fb5f595679e58