Process crash via unchecked ZIP comment length
Published Aug 29, 2022 · Updated Aug 3, 2024
Heap buffer overflow in AdvanceCOMP 2.3 allows attackers to crash advzip by inducing a user to process a crafted ZIP archive. In zip::open, the end-of-central-directory comment length is passed to data_dup() without first checking that the stated bytes remain in the input buffer. The input must be processed locally; the documented consequence is a command-line process crash, and Debian assesses no broader security impact.
Summary
What happened
Heap buffer overflow in AdvanceCOMP 2.3 allows attackers to crash advzip by inducing a user to process a crafted ZIP archive. In zip::open, the end-of-central-directory comment length is passed to data_dup() without first checking that the stated bytes remain in the input buffer. The input must be processed locally; the documented consequence is a command-line process crash, and Debian assesses no broader security impact.
The record
- CVE
- CVE-2022-35016
- Published
- Aug 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- advzip -x heap-buffer-overflow sample No. 2proof 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