RHSA-2010:0838: Moderate: pki security and enhancement update

Published Nov 8, 2010
·
Updated

Red Hat Certificate System is an enterprise software system designed tomanage enterprise public key infrastructure (PKI) deployments. SimpleCertificate Enrollment Protocol (SCEP) is a PKI communication protocolused to automatically enroll certificates for network devices.The certificate authority allowed unauthenticated users to request theone-time PIN in an SCEP request to be decrypted. An attacker able to sniffan SCEP request from a network device could request the certificateauthority to decrypt the request, allowing them to obtain the one-timePIN. With this update, the certificate authority only handles decryptionrequests from authenticated registration authorities. (CVE-2010-3868)The certificate authority allowed the one-time PIN used in SCEP requeststo be re-used. An attacker possessing a valid SCEP enrollment one-time PINcould use it to generate an unlimited number of certificates.(CVE-2010-3869)The certificate authority used the MD5 hash algorithm to sign all SCEPprotocol responses. As MD5 is not collision resistant, an attacker coulduse this flaw to perform an MD5 chosen-prefix collision attack to generateattack-chosen output signed using the certificate authority's key.(CVE-2004-2761)This update also adds the following enhancements: New configuration options for the SCEP server can define the default and allowed encryption and hash algorithms. These options allow disabling usesof the weaker algorithms not required by network devices and preventpossible downgrade attacks. These can be configured by adding the followingoptions to the certificate authority's CS.cfg configuration file:ca.scep.encryptionAlgorithm=DES3 ca.scep.allowedEncryptionAlgorithms=DES3 ca.scep.hashAlgorithm=SHA1 ca.scep.allowedHashAlgorithms=SHA1,SHA256,SHA512 With this update, the certificate authority's SCEP server is disabled by default. The SCEP server can be enabled by adding the 'ca.scep.enable=true'option to the certificate authority's CS.cfg configuration file. A separate key pair can now be configured for use in SCEP communication. Previously, the main certificate authority's key pair was used for SCEPcommunication too. A designated SCEP key pair can be referenced by addinga new option, ca.scep.nickname=[scep certificate nickname], to thecertificate authority's CS.cfg configuration file. The certificate authority now allows the size of nonces used in SCEP requests to be restricted by adding a new option, ca.scep.nonceSizeLimit=[number of bytes], to the certificate authority's CS.cfg configurationfile. The limit is set to 16 bytes in the default CS.cfg configurationfile.All users of Red Hat Certificate System 8 should upgrade to these updatedpackages, which resolve these issues and add these enhancements.

Affected Software

5 affected componentsFixes available
redhat/pki-ca<8.0.7-1.el5
8.0.7-1.el5
redhat/pki-common<8.0.6-2.el5
8.0.6-2.el5
redhat/pki-util<8.0.5-1.el5
8.0.5-1.el5
redhat/pki-common-javadoc<8.0.6-2.el5
8.0.6-2.el5
redhat/pki-util-javadoc<8.0.5-1.el5
8.0.5-1.el5

Remediation

Event History

Nov 8, 2010
Advisory Published
via Red Hat·12:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2010:0838?

The severity of RHSA-2010:0838 is classified as moderate.

2

What products are affected by RHSA-2010:0838?

RHSA-2010:0838 affects the pki-ca, pki-common, pki-util, pki-common-javadoc, and pki-util-javadoc packages.

3

How do I fix RHSA-2010:0838?

To fix RHSA-2010:0838, update the affected packages to their respective remedial versions listed in the advisory.

4

Is there a workaround for RHSA-2010:0838?

There are no known workarounds for RHSA-2010:0838, the recommended action is to apply the updates.

5

When was RHSA-2010:0838 released?

RHSA-2010:0838 was released on December 15, 2010.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203