An OOB read flaw was found in the RFC 3161 Public Key Infrastructure Time-Stamp Protocol code of OpenSSL. An attacker could use this flaw to cause the openssl binary to crash when specially-crafted time-stamp file is parsed via the "openssl ts" command.
Created openssl101e tracking bugs for this issue:
Affects: epel-5 [bug 1359618]
Created openssl tracking bugs for this issue:
Affects: fedora-all [bug 1359616]
Created mingw-openssl tracking bugs for this issue:
Affects: fedora-all [bug 1359617]
The affected functionality is not used by the SSL/TLS implementation in OpenSSL. it is currently only used by the openssl command line tool, in its ts sub-command. Other applications using the OpenSSL library may also use this functionality, but it does not seem to be used by any other application in Red Hat Enterprise Linux.
Covered now by OpenSSL upstream security advisory and fixed in versions 1.0.1u and 1.0.2i.
OOB read in TS_OBJ_print_bio() (CVE-2016-2180)
The function TS_OBJ_print_bio() misuses OBJ_obj2txt(): the return value is
the total length the OID text representation would use and not the amount
of data written. This will result in OOB reads when large OIDs are presented.
OpenSSL 1.0.2 users should upgrade to 1.0.2i
OpenSSL 1.0.1 users should upgrade to 1.0.1u
This issue was reported to OpenSSL on 21st July 2016 by Shi Lei (Gear Team,
Qihoo 360 Inc.). The fix was developed by Stephen Henson of the OpenSSL
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6
Red Hat Enterprise Linux 7
Via RHSA-2016:1940 https://rhn.redhat.com/errata/RHSA-2016-1940.html