Description
statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a denial of service (use-after-free) or possibly execute arbitrary code via a crafted TLS session.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a n/a
n/aaffected
References
- https://www.tenable.com/security/tns-2016-20 ↗
- http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html ↗
- https://www.openssl.org/news/secadv/20160926.txt ↗
- https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03856en_us ↗
- http://www-01.ibm.com/support/docview.wss?uid=swg21995039 ↗
- http://www.securitytracker.com/id/1036885 ↗
- http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html ↗
- https://www.tenable.com/security/tns-2016-16 ↗
- https://git.openssl.org/?p=openssl.git%3Ba=commit%3Bh=acacbfa7565c78d2273c0b2a2e5e803f44afefeb ↗
- http://www.securityfocus.com/bid/93177 ↗
- http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html ↗
- https://bto.bluecoat.com/security-advisory/sa132 ↗
- http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html ↗
- http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10759 ↗