{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-51746 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-51746 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-51746 is a high-severity memory corruption vulnerability in Siemens Jt2go, published on 9 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-51746 and fix it if it is affected.\n\nWhat it is: CVE-2023-51746 is a high-severity memory corruption vulnerability in Siemens Jt2go, published on 9 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-51746 in the wild and no public exploit code.\n\nAffected product: Siemens Jt2go. 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-51746/ (Markdown: https://insights.sbomify.com/CVE-2023-51746/index.md)","id":"CVE-2023-51746","markdown":"https://insights.sbomify.com/CVE-2023-51746/index.md","name":"CVE-2023-51746","record":{"aliases":["GHSA-265c-wv4g-2q6r"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Siemens CAD viewer","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening malicious CGM files in Siemens JT2Go or Teamcenter Visualization.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"siemens","cpe":[{"product":"jt2go","vendor":"siemens"},{"product":"teamcenter_visualization","vendor":"siemens"}],"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/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A vulnerability has been identified in JT2Go (All versions \u003c V14.3.0.6), Teamcenter Visualization V13.3 (All versions \u003c V13.3.0.13), Teamcenter Visualization V14.1 (All versions \u003c V14.1.0.12), Teamcenter Visualization V14.2 (All versions \u003c V14.2.0.9), Teamcenter Visualization V14.3 (All versions \u003c V14.3.0.6). The affected applications contain a stack overflow vulnerability while parsing specially crafted CGM files. This could allow an attacker to execute code in the context of the current process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in JT2Go","id":"CVE-2023-51746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"siemens:jt2go","products":["siemens:jt2go","siemens:teamcenter_visualization"],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"SMTP smuggling in Apache James","id":"CVE-2023-51747"},"packages":[],"prev":{"headline":"Memory corruption in JT2Go","id":"CVE-2023-51745"},"products":["JT2Go","Teamcenter Visualization V13.3","Teamcenter Visualization V14.1","Teamcenter Visualization V14.2","Teamcenter Visualization V14.3"],"published":"2024-01-09","related":[{"cvss_score":8.8,"headline":"Memory corruption in JT2Go","id":"CVE-2020-26980","kev_date_added":null,"published":"2021-01-12"},{"cvss_score":8.8,"headline":"Memory corruption in JT2Go","id":"CVE-2020-26982","kev_date_added":null,"published":"2021-01-12"},{"cvss_score":8.8,"headline":"Memory corruption in JT2Go","id":"CVE-2020-26983","kev_date_added":null,"published":"2021-01-12"},{"cvss_score":8.8,"headline":"Memory corruption in JT2Go","id":"CVE-2020-26984","kev_date_added":null,"published":"2021-01-12"},{"cvss_score":8.8,"headline":"Memory corruption in JT2Go","id":"CVE-2020-26985","kev_date_added":null,"published":"2021-01-12"},{"cvss_score":8.8,"headline":"Memory corruption in JT2Go","id":"CVE-2020-26986","kev_date_added":null,"published":"2021-01-12"},{"cvss_score":8.8,"headline":"Memory corruption in JT2Go","id":"CVE-2020-26987","kev_date_added":null,"published":"2021-01-12"}],"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":"total"},"state":"PUBLISHED","updated":"2024-09-04","vendors":["Siemens"]},"summary":"Attackers can execute arbitrary code by tricking users into opening malicious CGM files in Siemens JT2Go or Teamcenter Visualization.","url":"https://insights.sbomify.com/CVE-2023-51746/"}