Vulnerability Note VU#336446

OpenCA libCheckSignature function fails to properly verify the signature of certificates

Original Release date: 19 Jan 2004 | Last revised: 22 Jan 2004

Overview

OpenCA may accept a signature from a certificate if the certificate's chain is trusted by the chain directory of OpenCA.

Description

The OpenCA PKI Development Project is a Certification Authority. A vulnerability exists in the way the libCheckSignature function compares the certificate in the database and the certificate of the signer.

From the OpenCA Security Advisory:

    The comparison of the certificate in the database and the certificate of the signer was only performed on base of the serial of the certificate. The design of the function can cause the acceptance
    of a signature if the chain of the signature can create a trust relationship to the chain directory of OpenCA and a certificate with a matching serial exists in the used PKI.

See the OpenCA Security Advisory for further details.

Impact

OpenCA may accept the signature of a certificate if the certificate's chain is trusted by the chain directory of OpenCA. This could allow a certificate from another PKI to authorize operations on the used PKI.

Solution


Upgrade
OpenCA version 0.9.1.7 has been released to address this vulnerability.

Apply Patch
OpenCA has supplied a patch which resolves this issue.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
OpenCAAffected-19 Jan 2004
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

Thanks to OpenCA for the information contained in their security advisory. OpenCA credits Alexandru Matei for discovering this vulnerability.

This document was written by Damon Morda.

Other Information

  • CVE IDs: CAN-2004-0004
  • Date Public: 16 Jan 2004
  • Date First Published: 19 Jan 2004
  • Date Last Updated: 22 Jan 2004
  • Severity Metric: 1.69
  • Document Revision: 15

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.