Hide Forgot
It was found that doapr_outch function in crypto/bio/b_print.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g does not verify that a certain memory allocation succeeds, which allows remote attackers to cause a denial of service (out-of-bounds write or memory consumption) or possibly have unspecified other impact via a long string, as demonstrated by a large amount of ASN.1 data. This issues is different than CVE-2016-0799. Upstream patch: https://git.openssl.org/?p=openssl.git;a=commit;h=578b956fe741bf8e84055547b1e83c28dd902c73
Created openssl101e tracking bugs for this issue: Affects: epel-5 [bug 1314766]
Created openssl tracking bugs for this issue: Affects: fedora-all [bug 1314764]
Created mingw-openssl tracking bugs for this issue: Affects: fedora-all [bug 1314765]
Can we do this in higher priority? Clients concern this seriously as it is related to openssl. Thanks.
Note that the patch for CVE-2016-0799 fixes also this issue.
Acknowledgments: Name: the OpenSSL project Upstream: Guido Vranken
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2016:0722 https://rhn.redhat.com/errata/RHSA-2016-0722.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2016:0996 https://rhn.redhat.com/errata/RHSA-2016-0996.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.7 Extended Update Support Via RHSA-2016:2073 https://rhn.redhat.com/errata/RHSA-2016-2073.html
This issue has been addressed in the following products: Via RHSA-2016:2957 https://rhn.redhat.com/errata/RHSA-2016-2957.html