Truncated packet could crash via OOB read
15Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 58%
exploitation probability
58%top 1% of all CVEs
observed exploitation
nono source reports it
If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k.
Affected products
OpenSSL · OpenSSLReferences
http://rhn.redhat.com/errata/RHSA-2017-0286.htmlhttps://access.redhat.com/errata/RHSA-2018:2185https://access.redhat.com/errata/RHSA-2018:2186https://access.redhat.com/errata/RHSA-2018:2187https://github.com/openssl/openssl/commit/00d965474b22b54e4275232bc71ee0c699c5cd21https://security.FreeBSD.org/advisories/FreeBSD-SA-17:02.openssl.aschttps://security.gentoo.org/glsa/201702-07https://security.netapp.com/advisory/ntap-20171019-0002/https://security.paloaltonetworks.com/CVE-2017-3731https://source.android.com/security/bulletin/pixel/2017-11-01https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03838en_ushttps://www.openssl.org/news/secadv/20170126.txt