Arbitrary code execution via wrapped len-array allocation
Published Jan 8, 2024 · Updated Nov 4, 2025
Integer overflow in GTKWave 3.3.115 LXT2 facgeometry parsing allows attackers to execute arbitrary code through a crafted .lxt2 file. In lxt2_rd_init, the file-controlled numfacs count can wrap the len-array allocation size before a loop writes entries past the undersized heap buffer. Execution requires a victim to open the file in the GUI or an affected LXT2 utility, after which code runs with that user's privileges.
Summary
What happened
Integer overflow in GTKWave 3.3.115 LXT2 facgeometry parsing allows attackers to execute arbitrary code through a crafted .lxt2 file. In lxt2_rd_init, the file-controlled numfacs count can wrap the len-array allocation size before a loop writes entries past the undersized heap buffer. Execution requires a victim to open the file in the GUI or an affected LXT2 utility, after which code runs with that user's privileges.
The record
- CVE
- CVE-2023-39274
- Published
- Jan 8, 2024
- Updated
- Nov 4, 2025
- Vendor
- GTKWave
- Product
- GTKWave
- Classifications
- CWE-190, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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=3.3.115
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.
Public exploit references
No public exploit references are available in this record.
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