Application crash via incorrect traversal-prefix loop
Published Mar 11, 2021 · Updated Aug 3, 2024
A denial of service in Go 1.16.0 archive/zip allows attackers to crash applications that call Reader.Open on a crafted ZIP archive. The toValidName function tests the unchanged original filename while repeatedly shortening its cleaned path, so a leading ../ prefix eventually triggers a panic. An application must parse an attacker-supplied archive through Reader.Open; an unrecovered panic terminates the affected process.
Summary
What happened
A denial of service in Go 1.16.0 archive/zip allows attackers to crash applications that call Reader.Open on a crafted ZIP archive. The toValidName function tests the unchanged original filename while repeatedly shortening its cleaned path, so a leading ../ prefix eventually triggers a panic. An application must parse an attacker-supplied archive through Reader.Open; an unrecovered panic terminates the affected process.
The record
- CVE
- CVE-2021-27919
- Published
- Mar 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 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.
Weakness, pattern, technique
Public exploit references
- Go TestCVE202127919 regression testproof 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