Skip to navigation

CVE Database

CVE-2012-2333

Impact: Moderate
Public: 2012-05-10
Bugzilla: 820686: CVE-2012-2333 openssl: record length handling integer underflow
IAVA: 2013-A-0113

Details

The MITRE CVE dictionary describes this issue as:

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.

Find out more about CVE-2012-2333 from the MITRE CVE dictionary and NIST NVD.

Statement

This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3 and 4. The openssl versions in Red Hat Enterprise Linux 5 and 6 were partially affected, as they support DTLS, but they do not support TLS 1.1 and TLS 1.2. This issue was addressed in Red Hat Enterprise Linux 5 and 6 via RHSA-2012:0699.

CVSS v2 metrics

Base Score: 5.0
Base Metrics: AV:N/AC:L/Au:N/C:N/I:N/A:P
Access Vector: Network
Access Complexity: Low
Authentication: None
Confidentiality Impact: None
Integrity Impact: None
Availability Impact: Partial

Find out more about Red Hat support for the Common Vulnerability Scoring System (CVSS).

Red Hat security errata

Platform Errata Release Date
Red Hat Enterprise Linux version 5 (openssl) RHSA-2012:0699 May 29, 2012
Red Hat Enterprise Linux version 6 (openssl) RHSA-2012:0699 May 29, 2012
Red Hat JBoss Enterprise Application Platform 5.1 (openssl) RHSA-2012:1307 September 24, 2012
Red Hat JBoss Enterprise Application Platform 6.0 (openssl) RHSA-2012:1308 September 24, 2012
Red Hat JBoss Web Server 1.0 RHSA-2012:1306 September 24, 2012

External References

http://openssl.org/news/secadv_20120510.txt

Acknowledgements

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

This page is generated automatically and has not been checked for errors or omissions.

For clarification or corrections please contact the Red Hat Security Response Team.