CVE-2012-2333: Medium severity openssl vulnerability

Published May 10, 2012
·
Updated

Integer underflow in OpenSSL before 0.9.8x, 1.0.0 before 1.0.0j, and 1.0.1 before 1.0.1c, when TLS 1.1, TLS 1.2, or DTLS is used with CBC encryption, allows remote attackers to cause a denial of service (buffer over-read) or possibly have unspecified other impact via a crafted TLS packet that is not properly handled during a certain explicit IV calculation.

Other sources

It was discovered that OpenSSL did not properly handle TLS record length values from the received TLS packets. After subtracting the number of padding bytes from the record length value, it did not check the resulting record length before subtracting the size of explicit IV (initialization vector for CBC encryption modes). This could result in an integer underflow of the record length value, leading to a buffer over-read and out-of-bounds access. A remote TLS peer could use this to crash an application using OpenSSL (usually a TLS or DTLS server) by sending a specially TLS packet.

Explicit IV is used in TLS 1.2, 1.1 and DTLS. The openssl packages in Red Hat Enterprise Linux 3, 4, 5, and 6 only support TLS 1.0 and do not support TLS 1.1 and 1.2 and hence are not affected by the TLS part of this problem. TLS versions 1.1 and 1.2 support was introduced upstream in OpenSSL version 1.0.1. That version is currently only available in Fedora Rawhide/18.

The support for DTLS (Datagram Transport Layer Security) is enabled in openssl packages in Red Hat Enterprise Linux 5 and 6 and those versions are affected by the DTLS part of this problem. Applications using openssl packages in Red Hat Enterprise Linux 5 and 6 to provide TLS/SSL service (such as httpd) are not affected by this issue.

Upstream fix: http://cvs.openssl.org/chngview?cn=22538 (0.9.8) http://cvs.openssl.org/chngview?cn=22547 (1.0.1)

This was fixed upstream in versions: 0.9.8x, 1.0.0j and 1.0.1c

Acknowledgement:

Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Codenomicon as the original reporter.

Red Hat

Affected Software

101 affected componentsFixes available
redhat/openssl<0.9.8
0.9.8
redhat/openssl<1.0.0
1.0.0
OpenSSL OpenSSL<=0.9.8w
OpenSSL OpenSSL=0.9.1c
OpenSSL OpenSSL=0.9.2b
OpenSSL OpenSSL=0.9.3
OpenSSL OpenSSL=0.9.3a
OpenSSL OpenSSL=0.9.4
OpenSSL OpenSSL=0.9.5
OpenSSL OpenSSL=0.9.5-beta1
OpenSSL OpenSSL=0.9.5-beta2
OpenSSL OpenSSL=0.9.5a
OpenSSL OpenSSL=0.9.5a-beta1
OpenSSL OpenSSL=0.9.5a-beta2
OpenSSL OpenSSL=0.9.6
OpenSSL OpenSSL=0.9.6-beta1
OpenSSL OpenSSL=0.9.6-beta2
OpenSSL OpenSSL=0.9.6-beta3
OpenSSL OpenSSL=0.9.6a
OpenSSL OpenSSL=0.9.6a-beta1
OpenSSL OpenSSL=0.9.6a-beta2
OpenSSL OpenSSL=0.9.6a-beta3
OpenSSL OpenSSL=0.9.6b
OpenSSL OpenSSL=0.9.6c
OpenSSL OpenSSL=0.9.6d
OpenSSL OpenSSL=0.9.6e
OpenSSL OpenSSL=0.9.6f
OpenSSL OpenSSL=0.9.6g
OpenSSL OpenSSL=0.9.6h
OpenSSL OpenSSL=0.9.6i
OpenSSL OpenSSL=0.9.6j
OpenSSL OpenSSL=0.9.6k
OpenSSL OpenSSL=0.9.6l
OpenSSL OpenSSL=0.9.6m
OpenSSL OpenSSL=0.9.7
OpenSSL OpenSSL=0.9.7-beta1
OpenSSL OpenSSL=0.9.7-beta2
OpenSSL OpenSSL=0.9.7-beta3
OpenSSL OpenSSL=0.9.7-beta4
OpenSSL OpenSSL=0.9.7-beta5
OpenSSL OpenSSL=0.9.7-beta6
OpenSSL OpenSSL=0.9.7a
OpenSSL OpenSSL=0.9.7b
OpenSSL OpenSSL=0.9.7c
OpenSSL OpenSSL=0.9.7d
OpenSSL OpenSSL=0.9.7e
OpenSSL OpenSSL=0.9.7f
OpenSSL OpenSSL=0.9.7g
OpenSSL OpenSSL=0.9.7h
OpenSSL OpenSSL=0.9.7i
OpenSSL OpenSSL=0.9.7j
OpenSSL OpenSSL=0.9.7k
OpenSSL OpenSSL=0.9.7l
OpenSSL OpenSSL=0.9.7m
OpenSSL OpenSSL=0.9.8
OpenSSL OpenSSL=0.9.8a
OpenSSL OpenSSL=0.9.8b
OpenSSL OpenSSL=0.9.8c
OpenSSL OpenSSL=0.9.8d
OpenSSL OpenSSL=0.9.8e
OpenSSL OpenSSL=0.9.8f
OpenSSL OpenSSL=0.9.8g
OpenSSL OpenSSL=0.9.8h
OpenSSL OpenSSL=0.9.8i
OpenSSL OpenSSL=0.9.8j
OpenSSL OpenSSL=0.9.8k
OpenSSL OpenSSL=0.9.8l
OpenSSL OpenSSL=0.9.8m
OpenSSL OpenSSL=0.9.8m-beta1
OpenSSL OpenSSL=0.9.8n
OpenSSL OpenSSL=0.9.8o
OpenSSL OpenSSL=0.9.8p
OpenSSL OpenSSL=0.9.8q
OpenSSL OpenSSL=0.9.8r
OpenSSL OpenSSL=0.9.8s
OpenSSL OpenSSL=0.9.8t
OpenSSL OpenSSL=0.9.8u
OpenSSL OpenSSL=0.9.8v
redhat Openssl=0.9.6-15
redhat Openssl=0.9.6b-3
redhat Openssl=0.9.7a-2
OpenSSL OpenSSL=1.0.0
OpenSSL OpenSSL=1.0.0-beta1
OpenSSL OpenSSL=1.0.0-beta2
OpenSSL OpenSSL=1.0.0-beta3
OpenSSL OpenSSL=1.0.0-beta4
OpenSSL OpenSSL=1.0.0-beta5
OpenSSL OpenSSL=1.0.0a
OpenSSL OpenSSL=1.0.0b
OpenSSL OpenSSL=1.0.0c
OpenSSL OpenSSL=1.0.0d
OpenSSL OpenSSL=1.0.0e
OpenSSL OpenSSL=1.0.0f
OpenSSL OpenSSL=1.0.0g
OpenSSL OpenSSL=1.0.0h
OpenSSL OpenSSL=1.0.1
OpenSSL OpenSSL=1.0.1-beta1
OpenSSL OpenSSL=1.0.1-beta2
OpenSSL OpenSSL=1.0.1-beta3
OpenSSL OpenSSL=1.0.1a
OpenSSL OpenSSL=1.0.1b

Event History

May 10, 2012
Data Sourced
via Red Hat·05:18 PM
DescriptionSeverityAffected Software
May 14, 2012
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-2333?

The severity of CVE-2012-2333 is critical as it allows remote attackers to cause a denial of service through buffer over-read.

2

How do I fix CVE-2012-2333?

To fix CVE-2012-2333, upgrade OpenSSL to version 0.9.8x, 1.0.0j, or 1.0.1c or later.

3

What versions of OpenSSL are affected by CVE-2012-2333?

CVE-2012-2333 affects OpenSSL versions prior to 0.9.8x, 1.0.0 before 1.0.0j, and 1.0.1 before 1.0.1c.

4

What types of attacks are possible due to CVE-2012-2333?

CVE-2012-2333 allows attackers to cause a denial of service or potentially lead to unspecified other impacts via crafted TLS packets.

5

Is CVE-2012-2333 relevant for TLS 1.1 and TLS 1.2 users?

Yes, CVE-2012-2333 is particularly relevant for users of TLS 1.1 and TLS 1.2 with CBC encryption.

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