Converter crash via genptk_text stack-buffer overwrite
Published Aug 10, 2021 · Updated Aug 4, 2024
Stack-based buffer overflow in Fig2dev Project fig2dev 3.2.7b allows attackers to crash the converter via a crafted Xfig file. While generating PTK output, genptk_text in genptk.c writes a byte beyond the 2,048-byte stfp stack buffer when processing file content. A user must cause the crafted file to be converted to PTK; the demonstrated consequence is process termination, not code execution.
Summary
What happened
Stack-based buffer overflow in Fig2dev Project fig2dev 3.2.7b allows attackers to crash the converter via a crafted Xfig file. While generating PTK output, genptk_text in genptk.c writes a byte beyond the 2,048-byte stfp stack buffer when processing file content. A user must cause the crafted file to be converted to PTK; the demonstrated consequence is process termination, not code execution.
The record
- CVE
- CVE-2020-21675
- Published
- Aug 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-121, T1499, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 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
- AddressSanitizer-demonstrated crashing Xfig fileproof 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