Process crash via premature thread-state deallocation
Published Jun 10, 2021 · Updated Aug 3, 2024
Null pointer dereference in lrzip 0.631 allows local users to crash the command-line process by processing a crafted compressed file. When a chunk decompression fails, close_stream_in releases stream and pthread state before every worker thread exits, leaving ucompthread to dereference invalid state. Local execution must process the crafted archive; the demonstrated consequence is termination of the lrzip process.
Summary
What happened
Null pointer dereference in lrzip 0.631 allows local users to crash the command-line process by processing a crafted compressed file. When a chunk decompression fails, close_stream_in releases stream and pthread state before every worker thread exits, leaving ucompthread to dereference invalid state. Local execution must process the crafted archive; the demonstrated consequence is termination of the lrzip process.
The record
- CVE
- CVE-2021-27345
- Published
- Jun 10, 2021
- Updated
- Aug 3, 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 3, 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-stream1523 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