Code execution via unchecked EVCD length index
Published Jan 8, 2024 · Updated Nov 4, 2025
Improper array index validation in GTKWave 3.3.115 allows attackers to execute arbitrary code through a crafted EVCD file. In evcd_main, an attacker-controlled $var length is stored in vcd_ids and later used without bounds checking to index bin_fixbuff, enabling an out-of-bounds NULL-byte write. Execution requires a victim to open the file with the evcd2vcd utility, and repeated stack writes can corrupt process memory within that user's context.
Summary
What happened
Improper array index validation in GTKWave 3.3.115 allows attackers to execute arbitrary code through a crafted EVCD file. In evcd_main, an attacker-controlled $var length is stored in vcd_ids and later used without bounds checking to index bin_fixbuff, enabling an out-of-bounds NULL-byte write. Execution requires a victim to open the file with the evcd2vcd utility, and repeated stack writes can corrupt process memory within that user's context.
The record
- CVE
- CVE-2023-34087
- Published
- Jan 8, 2024
- Updated
- Nov 4, 2025
- Vendor
- GTKWave
- Product
- GTKWave
- Classifications
- CWE-119, T1203
- 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.
Weakness, pattern, technique
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