CVE-2010-0742: High severity OpenSSL OpenSSL vulnerability
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
Remediation
Patch Available
Event History
Frequently Asked Questions
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.
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.
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.
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.
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.