OpenSSL accepts unsolicited client certificate messages

2003-09-30T00:00:00
ID VU:732952
Type cert
Reporter CERT
Modified 2003-10-01T22:26:00

Description

Overview

OpenSSL accepts unsolicited client certificate messages. This could allow an attacker to exploit underlying vulnerabilities in client certificate handling.

Description

OpenSSL implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols and includes a general-purpose cryptographic library. SSL and TLS are commonly used to provide authentication, encryption, integrity, and non-repudiation services to network applications such as HTTP, IMAP, POP3, LDAP, and others. Clients and servers exchange authentication information in X.509 certificates.

Both the (obsolete) SSL 3.0 standard and RFC 2246 (TLSv1) state that a client certificate message "...is only sent if the server requests a certificate." To minimize the opportunity for attacks, an SSL/TLS service should ignore unsolicited client certificate messages.

OpenSSL versions prior to 0.9.7c and 0.9.6k accept unsolicited client certificate messages. This allows an attacker to attempt to exploit several vulnerabilities using specially crafted client certificate messages.

From the OpenSSL advisory:

> > 4. Due to an error in the SSL/TLS protocol handling, a server will parsea client certificate when one is not specifically requested. This byitself is not strictly speaking a vulnerability but it does mean thatall SSL/TLS servers that use OpenSSL can be attacked usingvulnerabilities 1, 2 and 3 even if they don't enable client authentication.

Vulnerability 1 refers to VU#935264. Vulnerability 2 refers to both VU#255484 and VU#380864. Vulnerability 3 refers to VU#686224.

Impact

Using specially crafted client certificate messages, a remote attacker can attempt to exploit underlying vulnerabilities in SSL/TLS ASN.1 parsing implementations. The impacts of these vulnerabilities (VU#935264, VU#255484, VU#380864, and VU#686224) are denial of service and possible execution of arbitrary code.


Solution

Upgrade or Patch
Upgrade to OpenSSL 0.9.7c or 0.9.6k. Alternatively, upgrade or apply a patch as specified by your vendor. Further information is available in an advisory from OpenSSL. Note that it is necessary to recompile any applications that are statically linked to OpenSSL libraries.


Vendor Information

732952

Filter by status: All Affected Not Affected Unknown

Filter by content: __ Additional information available

__ Sort by: Status Alphabetical

Expand all

Javascript is disabled. Click here to view vendors.

OpenSSL __ Affected

Updated: September 30, 2003

Status

Affected

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see <<http://www.openssl.org/news/secadv_20030930.txt>>.

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

CVSS Metrics

Group | Score | Vector
---|---|---
Base | |
Temporal | |
Environmental | |

References

  • <http://www.openssl.org/news/secadv_20030930.txt>
  • <http://wp.netscape.com/eng/ssl3/draft302.txt>
  • <http://www.ietf.org/rfc/rfc2246.txt>

Acknowledgements

Information used in this document came from OpenSSL and NISCC.

This document was written by Art Manion.

Other Information

CVE IDs: | None
---|---
CERT Advisory: | CA-2003-26
Severity Metric: | 2.53
Date Public: | 2003-09-04
Date First Published: | 2003-09-30
Date Last Updated: | 2003-10-01 22:26 UTC
Document Revision: | 15