Code execution via literal-run length overflow
Published Feb 12, 2020 · Updated Aug 6, 2024
Integer overflow in Oberhumer LZO before 2.07 allows remote attackers to execute arbitrary code via crafted compressed input on 32-bit platforms. In lzo1x_decompress_safe and related safe decompressor variants, repeated zero bytes add 255 to the literal length until it wraps, so NEED_OP validates the truncated size before literals are copied. The application must decompress more than 16 MiB of attacker-controlled data in one call; a crash is practical, while code execution is highly specialized and impractical.
Summary
What happened
Integer overflow in Oberhumer LZO before 2.07 allows remote attackers to execute arbitrary code via crafted compressed input on 32-bit platforms. In lzo1x_decompress_safe and related safe decompressor variants, repeated zero bytes add 255 to the literal length until it wraps, so NEED_OP validates the truncated size before literals are copied. The application must decompress more than 16 MiB of attacker-controlled data in one call; a crash is practical, while code execution is highly specialized and impractical.
The record
- CVE
- CVE-2014-4607
- Published
- Feb 12, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- LMS-2014-06-16-1 technical trigger demonstrationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo