Process crash via duplicate archive-buffer cleanup
Published Feb 9, 2021 · Updated Aug 5, 2024
Use-after-free in libzip 1.2.0 allows attackers to crash a consuming application that opens a malformed ZIP archive. An error path in _zip_dirent_read frees its temporary archive buffer, then later cleanup calls _zip_buffer_free on the same allocation and reads released heap memory. Reaching the flaw requires an application to open the crafted archive; the demonstrated consequence is process termination under AddressSanitizer.
Summary
What happened
Use-after-free in libzip 1.2.0 allows attackers to crash a consuming application that opens a malformed ZIP archive. An error path in _zip_dirent_read frees its temporary archive buffer, then later cleanup calls _zip_buffer_free on the same allocation and reads released heap memory. Reaching the flaw requires an application to open the crafted archive; the demonstrated consequence is process termination under AddressSanitizer.
The record
- CVE
- CVE-2019-17582
- Published
- Feb 9, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1203
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
- libzip _zip_buffer_free use-after-free testcaseproof 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