{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-37416 exists.","fix":"Apply the vendor's patch.","what":"CVE-2023-37416 is a high-severity memory corruption 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-37416 and fix it if it is affected.\n\nWhat it is: CVE-2023-37416 is a high-severity memory corruption 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-37416 exists.\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-37416/ (Markdown: https://insights.sbomify.com/CVE-2023-37416/index.md)","id":"CVE-2023-37416","markdown":"https://insights.sbomify.com/CVE-2023-37416/index.md","name":"CVE-2023-37416","record":{"aliases":["DEBIAN-CVE-2023-37416","GHSA-89gm-h4q5-gp3r","UBUNTU-CVE-2023-37416"],"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 execute arbitrary code by tricking a user into opening a malicious VCD file in GTKWave.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"gtkwave","vendor":"tonybybell"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Multiple out-of-bounds write vulnerabilities exist in the VCD parse_valuechange portdump 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 the out-of-bounds write when triggered via the GUI's legacy VCD parsing code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in GTKWave","id":"CVE-2023-37416","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"tonybybell:gtkwave","products":["tonybybell:gtkwave"],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in GTKWave","id":"CVE-2023-37417"},"packages":[],"prev":{"headline":"Apache Airflow Apache Hive Provider: Improper Input Validation in Hive Provider with proxy_user","id":"CVE-2023-37415"},"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["GTKWave"]},"summary":"An attacker can execute arbitrary code by tricking a user into opening a malicious VCD file in GTKWave.","url":"https://insights.sbomify.com/CVE-2023-37416/"}