Truncated packet could crash via OOB read
OpenSSL · OpenSSL
A truncated packet flaw in OpenSSL allows an out-of-bounds read in SSL/TLS servers and clients running on 32-bit hosts when a specific cipher is in use, typically causing a crash. Triggering it requires only that the affected cipher (CHACHA20/POLY1305 in OpenSSL 1.1.0, or RC4-MD5 in 1.0.2) is negotiated, with no stated authentication or user interaction.
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.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 4 May 2017. No public exploit code or confirmed exploitation is recorded.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linkedNo ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.