Memory corruption via NUL-triggered buffer underread
Published Apr 23, 2025 · Updated Jun 30, 2026
Stack-based buffer overflow in Xfig fig2dev 3.2.9a and earlier allows local users to corrupt memory through a crafted FIG file. In read_objects, an input line beginning with an ASCII NUL makes strlen return zero, after which the newline check reads buf[-1]. A low-privileged local user must supply the malformed input; the published assessment limits the reported consequence to data integrity.
Summary
What happened
Stack-based buffer overflow in Xfig fig2dev 3.2.9a and earlier allows local users to corrupt memory through a crafted FIG file. In read_objects, an input line beginning with an ASCII NUL makes strlen return zero, after which the newline check reads buf[-1]. A low-privileged local user must supply the malformed input; the published assessment limits the reported consequence to data integrity.
The record
- CVE
- CVE-2025-46398
- Published
- Apr 23, 2025
- Updated
- Jun 30, 2026
- Vendor
- Xfig
- Product
- fig2dev
- Classifications
- CWE-121
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 23, 2025CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record 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=0 <=3.2.9a
What conditions does exploitation require?
What is affected?
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
- Malformed FIG file proof of conceptproof of concept · unverified
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