Memory corruption via unchecked FST signal length
Published Jan 8, 2024 · Updated Nov 4, 2025
Heap-based buffer overflow in GTKWave 3.3.115 allows attackers to corrupt memory by inducing a victim to open a crafted FST file. In fstReaderIterBlocks2, an attacker-controlled signal_lens value is passed as len to fstWritex, which supplies it to memcpy without checking it against the remaining mu + sig_offs buffer. The victim must open the file; a mismatched beg_time reaches this path, producing an out-of-bounds heap write with process-crash or code-execution impact.
Summary
What happened
Heap-based buffer overflow in GTKWave 3.3.115 allows attackers to corrupt memory by inducing a victim to open a crafted FST file. In fstReaderIterBlocks2, an attacker-controlled signal_lens value is passed as len to fstWritex, which supplies it to memcpy without checking it against the remaining mu + sig_offs buffer. The victim must open the file; a mismatched beg_time reaches this path, producing an out-of-bounds heap write with process-crash or code-execution impact.
The record
- CVE
- CVE-2023-36747
- 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
- TALOS-2023-1793 crafted FST trigger analysisproof 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