Heap corruption via invalid suffix deallocation
Published Apr 15, 2022 · Updated Aug 3, 2024
Heap memory corruption in lrzip 0.640 allows attackers to corrupt process memory through unsafe command-line suffix handling. initialise_control stores the default .lrz suffix as a pointer to static storage, while cleanup and suffix changes pass that pointer to the heap deallocator. The flaw is reached when lrzip initializes or replaces a suffix and later frees the control structure; public evidence establishes heap corruption but not code execution.
Summary
What happened
Heap memory corruption in lrzip 0.640 allows attackers to corrupt process memory through unsafe command-line suffix handling. initialise_control stores the default .lrz suffix as a pointer to static storage, while cleanup and suffix changes pass that pointer to the heap deallocator. The flaw is reached when lrzip initializes or replaces a suffix and later frees the control structure; public evidence establishes heap corruption but not code execution.
The record
- CVE
- CVE-2022-28044
- Published
- Apr 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 15, 2022CVE 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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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