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/secadv_20100601.txt
Statement: Not vulnerable. These issues did not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux 3, 4, or 5.
Created openssl tracking bugs for this issue Affects: fedora-all [bug 598740]
(In reply to comment #0) > This has been corrected upstream via: > http://cvs.openssl.org/chngview?cn=19693 Relevant part is crypto/cms/cms_asn1.c change: http://cvs.openssl.org/filediff?f=openssl/crypto/cms/cms_asn1.c&v1=1.8&v2=1.8.6.1 Upstream bug report: http://rt.openssl.org/Ticket/Display.html?id=2211&user=guest&pass=guest
openssl-0.9.8n-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/openssl-0.9.8n-2.fc11
openssl-1.0.0a-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/openssl-1.0.0a-1.fc13
openssl-1.0.0a-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/openssl-1.0.0a-1.fc12
openssl-1.0.0a-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
openssl-1.0.0a-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
openssl-0.9.8n-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.