Process crash via malformed LZO archive
Published Jun 10, 2021 · Updated Aug 4, 2024
Null pointer dereference in lrzip 0.621 allows local users to crash the process by testing a crafted LZO-compressed archive. The lzo_decompress_buf path processes malformed archive data in lzo1x_decompress, which makes an invalid memory access and segfaults. Execution requires a user or automated workflow to test or decompress an attacker-supplied archive; the observed consequence is lrzip process termination.
Summary
What happened
Null pointer dereference in lrzip 0.621 allows local users to crash the process by testing a crafted LZO-compressed archive. The lzo_decompress_buf path processes malformed archive data in lzo1x_decompress, which makes an invalid memory access and segfaults. Execution requires a user or automated workflow to test or decompress an attacker-supplied archive; the observed consequence is lrzip process termination.
The record
- CVE
- CVE-2020-25467
- Published
- Jun 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
Public exploit references
- seg-stream589.zip proof-of-concept archiveproof 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