Cloudanix VulnDB

CVE-2023-39275

High · 7.8

CVSS

7.8

EPSS

0.4%

Published

Jan 8, 2024

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

Opening a specially made waveform file in this analysis tool can let an attacker take over the computer.

Exploit Available
Exploitation
Requires User Interaction
Attacker needs
User Interaction
Complexity
Low
Impact
Remote Code Execution
Component
Application
Class
Buffer Overflow
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Integer overflow during allocation of the `value` array in LXT2 facgeometry parsing allows out-of-bounds memory access and arbitrary code execution when a crafted .lxt2 file is opened.

Why it matters to the business

Attackers can gain full control of a user's workstation by tricking them into opening a malicious waveform file, leading to data theft, ransomware deployment, or further network compromise in environments that rely on GTKWave for signal analysis.

How an attack unfolds

An attacker creates a specially crafted .lxt2 file that triggers an integer overflow in the facgeometry value-array allocation routine. The victim is induced to open the file in GTKWave 3.3.115, causing the overflow to corrupt memory and execute attacker-supplied code.

How to fix it

Upgrade GTKWave to a version that corrects the LXT2 facgeometry parsing integer overflow. Until a fixed build is available, disable LXT2 import or restrict the application to trusted files only.

How to confirm the fix worked

Confirm GTKWave version is newer than 3.3.115, run the application against known-good and known-malicious LXT2 test files, and verify that the value-array allocation no longer overflows.

Typical attack path

  1. Craft malicious .lxt2 file exploiting the facgeometry integer overflow
  2. Deliver file via email, download link, or shared storage
  3. Victim opens file with vulnerable GTKWave instance
  4. Overflow occurs during array allocation leading to code execution

How to detect it

Review file-open logs and process-creation events for GTKWave accessing .lxt2 files from untrusted locations; look for subsequent crashes, unexpected child processes, or memory-corruption indicators shortly after file load.

What your security team should do

  • Immediately restrict GTKWave usage to verified files and consider alternative tools until patched builds are released
  • Add .lxt2 file-type blocking rules at email and web gateways
  • Monitor for any public exploit samples given the ExploitAvailable maturity rating

The record

Multiple integer overflow vulnerabilities exist in the LXT2 facgeometry parsing functionality of GTKWave 3.3.115. A specially crafted .lxt2 file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the integer overflow when allocating the `value` array.

Affected packages

Ecosystem Package Introduced Fixed
Debian:10 gtkwave 0 3.3.98+really3.3.118-0+deb10u1
Debian:11 gtkwave 0 3.3.104+really3.3.118-0+deb11u1
Debian:12 gtkwave 0 3.3.118-0.1~deb12u1
Debian:13 gtkwave 0 3.3.118-0.1
Ubuntu:16.04:LTS gtkwave 0 No fix
Ubuntu:18.04:LTS gtkwave 0 No fix
Ubuntu:20.04:LTS gtkwave 0 No fix
Ubuntu:22.04:LTS gtkwave 0 No fix
Ubuntu:24.04:LTS gtkwave 0 No fix
Ubuntu:24.10 gtkwave 0 No fix
Ubuntu:25.04 gtkwave 0 No fix
Ubuntu:25.10 gtkwave 0 No fix
Ubuntu:Pro:16.04:LTS gtkwave 0 No fix
Ubuntu:Pro:18.04:LTS gtkwave 0 No fix
Ubuntu:Pro:20.04:LTS gtkwave 0 No fix

Related vulnerabilities