CVE-2010-0742

Description

The Cryptographic Message Syntax (CMS) implementation in crypto/cms/cms_asn1.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.

Category

7.5
CVSS
Severity: High
CVSS 2.0 •
EPSS 16.78% Top 10%
Vendor Advisory marc.info Vendor Advisory secunia.com Vendor Advisory secunia.com Vendor Advisory vupen.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
http://rt.openssl.org/Ticket/Display.html?id=2211&user=guest&pass=guest
http://www.vupen.com/english/advisories/2010/1313 vdb entry patch vendor advisory
http://secunia.com/advisories/40024 third party advisory vendor advisory
http://secunia.com/advisories/42724 third party advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A12395 vdb entry signature
http://www.securityfocus.com/bid/40502 vdb entry
http://marc.info/?l=bugtraq&m=129138643405740&w=2 vendor advisory
http://www-01.ibm.com/support/docview.wss?uid=ssg1S1004564
http://www.vupen.com/english/advisories/2010/3105 vdb entry
https://lists.balabit.com/pipermail/syslog-ng-announce/2011-January/000101.html mailing list
http://cvs.openssl.org/filediff?f=openssl/crypto/cms/cms_asn1.c&v1=1.8&v2=1.8.6.1
http://secunia.com/advisories/57353 third party advisory
https://lists.balabit.com/pipermail/syslog-ng-announce/2011-January/000102.html mailing list
https://bugzilla.redhat.com/show_bug.cgi?id=598738
http://secunia.com/advisories/40000 third party advisory vendor advisory
https://kb.bluecoat.com/index?page=content&id=SA50
http://secunia.com/advisories/42733 third party advisory
http://secunia.com/advisories/42457 third party advisory
http://cvs.openssl.org/chngview?cn=19693
http://www.openssl.org/news/secadv_20100601.txt

Frequently Asked Questions

What is the severity of CVE-2010-0742?
CVE-2010-0742 has been scored as a high severity vulnerability.
How to fix CVE-2010-0742?
To fix CVE-2010-0742, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2010-0742 being actively exploited in the wild?
It is possible that CVE-2010-0742 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~17% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.