Memory corruption via malformed color definition
Published May 26, 2021 · Updated Aug 3, 2024
Out-of-bounds write in read_objects() in Xfig Project fig2dev 3.2.8a allows attackers to crash the process via a crafted FIG file. read_colordef() could retain an incompletely parsed user color; read_objects() then formatted its unchecked RGB values into the eight-byte gif_transparent buffer. A user must cause the utility to convert the crafted file; the demonstrated result is a crash, while the CNA also reports possible memory corruption.
Summary
What happened
Out-of-bounds write in read_objects() in Xfig Project fig2dev 3.2.8a allows attackers to crash the process via a crafted FIG file. read_colordef() could retain an incompletely parsed user color; read_objects() then formatted its unchecked RGB values into the eight-byte gif_transparent buffer. A user must cause the utility to convert the crafted file; the demonstrated result is a crash, while the CNA also reports possible memory corruption.
The record
- CVE
- CVE-2021-3561
- Published
- May 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- Xfig Project
- Product
- fig2dev
- Classifications
- CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=fig2dev 3.2.8a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- fig2dev_box_crash crafted-file 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