Process crash via stack-exhausting image buffer
Published Nov 2, 2021 · Updated Aug 4, 2024
Uncontrolled resource consumption in abhijitnathwani image-processing 0.1.0 allows local users to crash the program via a crafted image. A modified input image causes a locally allocated variable buffer to exhaust the process stack during image handling. Exploitation requires a user to process the malicious file, and the demonstrated consequence is a process crash rather than data disclosure or modification.
Summary
What happened
Uncontrolled resource consumption in abhijitnathwani image-processing 0.1.0 allows local users to crash the program via a crafted image. A modified input image causes a locally allocated variable buffer to exhaust the process stack during image handling. Exploitation requires a user to process the malicious file, and the demonstrated consequence is a process crash rather than data disclosure or modification.
The record
- CVE
- CVE-2020-21573
- Published
- Nov 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- crash.zip stack-exhaustion proof of conceptproof 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