{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-38651 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-38651 is a high-severity vulnerability in Tonybybell Gtkwave, published on 8 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-38651 and fix it if it is affected.\n\nWhat it is: CVE-2023-38651 is a high-severity vulnerability in Tonybybell Gtkwave, published on 8 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-38651 in the wild and no public exploit code.\n\nAffected product: Tonybybell Gtkwave. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-38651/ (Markdown: https://insights.sbomify.com/CVE-2023-38651/index.md)","id":"CVE-2023-38651","markdown":"https://insights.sbomify.com/CVE-2023-38651/index.md","name":"CVE-2023-38651","record":{"aliases":["DEBIAN-CVE-2023-38651","GHSA-w634-c25w-x24v","UBUNTU-CVE-2023-38651"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GTKWave waveform viewer","requires_auth":"none","summary":"An attacker can achieve code execution by tricking a user into opening a malicious VZT file in GTKWave due to an integer overflow.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"gtkwave","vendor":"tonybybell"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"Multiple integer overflow vulnerabilities exist in the VZT vzt_rd_block_vch_decode times parsing functionality of GTKWave 3.3.115. A specially crafted .vzt file can lead to memory corruption. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the integer overflow when num_time_ticks is zero.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Integer overflow in GTKWave","id":"CVE-2023-38651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"tonybybell:gtkwave","products":["tonybybell:gtkwave"],"type":"integer_overflow","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Integer overflow in GTKWave","id":"CVE-2023-38652"},"packages":[],"prev":{"headline":"Integer overflow in GTKWave","id":"CVE-2023-38650"},"products":["GTKWave"],"published":"2024-01-08","related":[{"cvss_score":7.8,"headline":"Memory corruption in GTKWave","id":"CVE-2023-34087","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":7.8,"headline":"Memory corruption in GTKWave","id":"CVE-2023-34436","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":7.8,"headline":"Integer overflow in GTKWave","id":"CVE-2023-35004","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":7.8,"headline":"Integer overflow in GTKWave","id":"CVE-2023-35057","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":7.8,"headline":"Memory corruption in GTKWave","id":"CVE-2023-35702","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":7.8,"headline":"Memory corruption in GTKWave","id":"CVE-2023-35703","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":7.8,"headline":"Memory corruption in GTKWave","id":"CVE-2023-35704","kev_date_added":null,"published":"2024-01-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["GTKWave"]},"summary":"An attacker can achieve code execution by tricking a user into opening a malicious VZT file in GTKWave due to an integer overflow.","url":"https://insights.sbomify.com/CVE-2023-38651/"}