CVE-2023-37921
Tonybybell Gtkwave 3.3.115
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-37921 is a high-severity Range Error (CWE-118) vulnerability in Tonybybell Gtkwave. Its CVSS base score is 7.8 (High).
Operationally, ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-41775
Vulnerability Data
Multiple arbitrary write vulnerabilities exist in the VCD sorted bsearch functionality of GTKWave 3.3.115. A specially crafted .vcd file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns…
more
the arbitrary write when triggered via the vcd2vzt conversion utility.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops out-of-bounds indices from being used on memory, arrays, or files.
Engineering principles such as bounds checking and safe pointer arithmetic stop range errors from being introduced in code.
Process isolation confines damage from an out-of-bounds access to a single domain without preventing the indexing flaw.
Memory protection limits the blast radius of a successful range error but does not stop the incorrect access itself.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle includes input validation and bounds checking that can prevent range errors.
Application security requirements can mandate bounds checking and safe indexing practices.
Secure architecture principles promote defensive coding that limits out-of-bounds access.
Secure coding standards directly require bounds checking and safe array access to prevent range errors.
Security testing can detect range errors through fuzzing and boundary-value analysis.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-118, a class-level weakness, and none of its children carries one either.