Process crash via unchecked font table index
Published Sep 16, 2021 · Updated Aug 4, 2024
Buffer overflow in fig2dev 3.2.7b allows attackers to crash the process by converting a crafted Fig file to eepic output. The setfigfont function in the genepic.c (E)EPIC output driver fails to validate a font value before using it to access global font data. A local user must cause fig2dev to process the crafted file; the supported consequence is a process crash, not confidentiality or integrity loss.
Summary
What happened
Buffer overflow in fig2dev 3.2.7b allows attackers to crash the process by converting a crafted Fig file to eepic output. The setfigfont function in the genepic.c (E)EPIC output driver fails to validate a font value before using it to access global font data. A local user must cause fig2dev to process the crafted file; the supported consequence is a process crash, not confidentiality or integrity loss.
The record
- CVE
- CVE-2020-21532
- Published
- Sep 16, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 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
- Xfig Ticket 64 crash 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