{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35057 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2023-35057 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-35057 and fix it if it is affected.\n\nWhat it is: CVE-2023-35057 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35057 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-35057/ (Markdown: https://insights.sbomify.com/CVE-2023-35057/index.md)","id":"CVE-2023-35057","markdown":"https://insights.sbomify.com/CVE-2023-35057/index.md","name":"CVE-2023-35057","record":{"aliases":["DEBIAN-CVE-2023-35057","GHSA-3mqx-ggcf-qxwg","UBUNTU-CVE-2023-35057"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GTKWave waveform viewer","requires_auth":"none","summary":"An attacker can cause memory corruption and potential code execution by tricking a user into opening a malicious LXT2 file in GTKWave.","user_interaction":"required","vuln_class":"integer_overflow"},"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-190","name":"Integer Overflow or Wraparound"}],"description":"An integer overflow vulnerability exists in the LXT2 lxt2_rd_trace value elements allocation 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 this vulnerability.","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":"Integer overflow in GTKWave","id":"CVE-2023-35057","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":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused","id":"CVE-2023-35058"},"packages":[],"prev":{"headline":"Memory corruption in YF325","id":"CVE-2023-35056"},"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":"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 cause memory corruption and potential code execution by tricking a user into opening a malicious LXT2 file in GTKWave.","url":"https://insights.sbomify.com/CVE-2023-35057/"}