VYPR
Unrated severityNVD Advisory· Published Jan 8, 2024· Updated Nov 4, 2025

CVE-2023-39413

CVE-2023-39413

Description

Multiple integer underflow vulnerabilities exist in the LXT2 lxt2_rd_iter_radix shift operation functionality of GTKWave 3.3.115. A specially crafted .lxt2 file can lead to memory corruption. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the integer underflow when performing the left shift operation.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Integer underflow in GTKWave 3.3.115's LXT2 parser leads to memory corruption when opening a crafted .lxt2 file.

Vulnerability

An integer underflow vulnerability exists in the lxt2_rd_iter_radix shift operation functionality of GTKWave version 3.3.115 [1]. The flaw resides in the LXT2 file parsing code within lxt2_read.c and can be triggered when a victim opens a specially crafted .lxt2 file [1]. The underflow occurs during a left shift operation, leading to memory corruption [1]. The vulnerable code is reachable via the GUI, the lxt2vcd conversion utility, rtlbrowse, and lxt2miner [1].

Exploitation

To exploit this vulnerability, an attacker must craft a malicious .lxt2 file that triggers the integer underflow during parsing [1]. The attacker then needs to convince a victim to open the file using GTKWave, either by double-clicking (as GTKWave registers mime types for its extensions) or through other social engineering [1]. No special privileges or network position is required beyond local file access [1]. User interaction is required as the victim must open the file [1].

Impact

Successful exploitation results in memory corruption [1]. Based on the CVSSv3 vector (AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H), the vulnerability can lead to a complete compromise of confidentiality, integrity, and availability (CIA) of the affected system, potentially allowing arbitrary code execution at the privilege level of the victim user [1].

Mitigation

As of the publication date (2024-01-08), no fixed version of GTKWave has been released [1]. Users are advised to exercise caution when opening .lxt2 files from untrusted sources and to monitor the GTKWave project for updates [1]. No workaround is explicitly provided in the available references [1].

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2
  • GTKWave/GTKWavellm-fuzzy
    Range: =3.3.115
  • GTKWave/GTKWavev5
    Range: 3.3.115

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

2

News mentions

0

No linked articles in our index yet.