Service crash via nonexistent compressed image name
Published Jan 12, 2022 · Updated Aug 4, 2024
Denial of service in fig2dev 3.2.8a and earlier allows local users to crash the converter via a crafted Fig input file. The open_stream function in readpics.c continues without a valid stream when a compression-suffixed image name refers to a nonexistent file, resulting in a null-address access. Execution requires the target to process the crafted Fig file, and successful exploitation terminates only the active fig2dev conversion process.
Summary
What happened
Denial of service in fig2dev 3.2.8a and earlier allows local users to crash the converter via a crafted Fig input file. The open_stream function in readpics.c continues without a valid stream when a compression-suffixed image name refers to a nonexistent file, resulting in a null-address access. Execution requires the target to process the crafted Fig file, and successful exploitation terminates only the active fig2dev conversion process.
The record
- CVE
- CVE-2021-37530
- Published
- Jan 12, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2022CVE 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
- SEGV-readpics.c-215-open_stream.zip reproducerproof 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