CVE-2010-0742: High severity OpenSSL OpenSSL vulnerability

Published Jun 1, 2010
·
Updated

From the upstream advisory [1]:

nvalid ASN1 module definition for CMS. =======================================

CMS structures containing OriginatorInfo are mishandled this can write to invalid memory addresses or free up memory twice (CVE-2010-0742).

This bug is only present in the CMS code: the older PKCS#7 code is not affected.

CMS is only present in OpenSSL 0.9.8h and later where it is disabled by default and 1.0.0 where it is enabled by default.

Users of OpenSSL CMS code should update to 0.9.8o or 1.0.0a which contains a patch to correct this issue.

Thanks to Ronald Moesbergen for reporting this issue.

This has been corrected upstream via:

http://cvs.openssl.org/chngview?cn=19693

[1] http://www.openssl.org/news/secadv20100601.txt

Other sources

The Cryptographic Message Syntax (CMS) implementation in crypto/cms/cmsasn1.c in OpenSSL before 0.9.8o and 1.x before 1.0.0a does not properly handle structures that contain OriginatorInfo, which allows context-dependent attackers to modify invalid memory locations or conduct double-free attacks, and possibly execute arbitrary code, via unspecified vectors.

Red Hat

Affected Software

72 affected components
OpenSSL OpenSSL=0.9.7-beta5
OpenSSL OpenSSL=0.9.7-beta3
OpenSSL OpenSSL=0.9.5a-beta2
OpenSSL OpenSSL=0.9.7-beta6
OpenSSL OpenSSL=0.9.8b
OpenSSL OpenSSL=0.9.7l
OpenSSL OpenSSL=0.9.6i
OpenSSL OpenSSL=0.9.8m
OpenSSL OpenSSL=0.9.3
OpenSSL OpenSSL=0.9.8c
OpenSSL OpenSSL=0.9.7-beta2
OpenSSL OpenSSL=0.9.7c
OpenSSL OpenSSL=0.9.5-beta1
OpenSSL OpenSSL=0.9.6d
OpenSSL OpenSSL=0.9.1c
OpenSSL OpenSSL=0.9.6
OpenSSL OpenSSL=0.9.7j
OpenSSL OpenSSL=0.9.6a
OpenSSL OpenSSL=0.9.8e
OpenSSL OpenSSL=0.9.4
OpenSSL OpenSSL=0.9.8g
OpenSSL OpenSSL=0.9.6a-beta2
OpenSSL OpenSSL=0.9.8k
OpenSSL OpenSSL=0.9.8d
OpenSSL OpenSSL=0.9.5a
OpenSSL OpenSSL=0.9.6f
OpenSSL OpenSSL=0.9.8j
OpenSSL OpenSSL=0.9.6-beta3
OpenSSL OpenSSL=0.9.6l
OpenSSL OpenSSL=0.9.7k
OpenSSL OpenSSL=0.9.7g
OpenSSL OpenSSL=0.9.6e
OpenSSL OpenSSL=0.9.7d
OpenSSL OpenSSL=0.9.8l
OpenSSL OpenSSL=0.9.7
OpenSSL OpenSSL=0.9.6b
OpenSSL OpenSSL=0.9.7e
OpenSSL OpenSSL=0.9.7b
OpenSSL OpenSSL=0.9.6a-beta1
OpenSSL OpenSSL=0.9.6k
OpenSSL OpenSSL=0.9.8a
OpenSSL OpenSSL=0.9.6g
OpenSSL OpenSSL=0.9.6-beta2
OpenSSL OpenSSL=0.9.7m
OpenSSL OpenSSL=0.9.7-beta4
OpenSSL OpenSSL=0.9.3a
OpenSSL OpenSSL<=0.9.8n
OpenSSL OpenSSL=0.9.6h
OpenSSL OpenSSL=0.9.7-beta1
OpenSSL OpenSSL=0.9.7i
OpenSSL OpenSSL=0.9.7h
OpenSSL OpenSSL=0.9.6j
OpenSSL OpenSSL=0.9.8
OpenSSL OpenSSL=0.9.7a
OpenSSL OpenSSL=0.9.6c
OpenSSL OpenSSL=0.9.6-beta1
OpenSSL OpenSSL=0.9.6m
OpenSSL OpenSSL=0.9.8i
OpenSSL OpenSSL=0.9.8f
OpenSSL OpenSSL=0.9.5-beta2
OpenSSL OpenSSL=0.9.8h
OpenSSL OpenSSL=0.9.2b
OpenSSL OpenSSL=0.9.5
OpenSSL OpenSSL=0.9.5a-beta1
OpenSSL OpenSSL=0.9.6a-beta3
OpenSSL OpenSSL=0.9.7f
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
OpenSSL OpenSSL=1.0.0-beta5

Event History

Jun 1, 2010
CVE Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionSeverity
Data Sourced
via Red Hat·11:05 PM
Affected Software
Jun 3, 2010
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:30 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2010-0742?

CVE-2010-0742 is considered a moderate severity vulnerability due to its potential to cause memory corruption and double-free attacks.

2

Which versions of OpenSSL are affected by CVE-2010-0742?

CVE-2010-0742 affects OpenSSL versions before 0.9.8o and 1.x before 1.0.0a.

3

How can I fix CVE-2010-0742?

To fix CVE-2010-0742, upgrade OpenSSL to version 0.9.8o or 1.0.0a or later.

4

What types of attacks can CVE-2010-0742 allow?

CVE-2010-0742 can allow attackers to modify invalid memory locations or conduct double-free attacks.

5

Is CVE-2010-0742 a critical vulnerability?

CVE-2010-0742 is not classified as a critical vulnerability but should still be addressed promptly to avoid security risks.

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