{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-47977 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-47977 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-47977 is a high-severity memory corruption vulnerability in Siemens JT Open, published on 14 Feb 2023. 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-2022-47977 and fix it if it is affected.\n\nWhat it is: CVE-2022-47977 is a high-severity memory corruption vulnerability in Siemens JT Open, published on 14 Feb 2023. 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-2022-47977 in the wild and no public exploit code.\n\nAffected product: Siemens JT Open. 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-2022-47977/ (Markdown: https://insights.sbomify.com/CVE-2022-47977/index.md)","id":"CVE-2022-47977","markdown":"https://insights.sbomify.com/CVE-2022-47977/index.md","name":"CVE-2022-47977","record":{"aliases":["GHSA-qw3q-69j5-5cf7"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Siemens JT utilities","requires_auth":"none","summary":"An attacker can execute arbitrary code by tricking a user into opening a specially crafted JT file in Siemens JT Open or JT Utilities.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"siemens","cpe":[{"product":"jt_open_toolkit","vendor":"siemens"},{"product":"jt_utilities","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-787","name":"Out-of-bounds Write"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A vulnerability has been identified in JT Open (All versions \u003c V11.2.3.0), JT Utilities (All versions \u003c V13.2.3.0). The affected application contains a memory corruption vulnerability while parsing specially crafted JT 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 JT Open","id":"CVE-2022-47977","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"IBM InfoSphere Information Server cross-site scripting","id":"CVE-2022-47983"},"packages":[],"prev":{"headline":"Auth bypass in EMUI","id":"CVE-2022-47976"},"products":["JT Open","JT Utilities"],"published":"2023-02-14","related":[{"cvss_score":7.8,"headline":"Memory corruption in JT Open","id":"CVE-2023-30796","kev_date_added":null,"published":"2023-08-08"},{"cvss_score":7.8,"headline":"Memory corruption in JT Open","id":"CVE-2023-29053","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":7.8,"headline":"Memory corruption in JT Open","id":"CVE-2022-47936","kev_date_added":null,"published":"2023-02-14"},{"cvss_score":7.8,"headline":"Memory corruption in JT Open","id":"CVE-2022-47935","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":7.8,"headline":"Null dereference in JTTK","id":"CVE-2022-41851","kev_date_added":null,"published":"2022-10-11"},{"cvss_score":7.8,"headline":"Memory corruption in JT Utilities","id":"CVE-2021-44430","kev_date_added":null,"published":"2021-12-14"}],"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":"2025-03-20","vendors":["Siemens"]},"summary":"An attacker can execute arbitrary code by tricking a user into opening a specially crafted JT file in Siemens JT Open or JT Utilities.","url":"https://insights.sbomify.com/CVE-2022-47977/"}