{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-28394 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28394 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28394 is a medium-severity memory corruption vulnerability in Siemens Jt2go, published on 9 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-28394 and fix it if it is affected.\n\nWhat it is: CVE-2020-28394 is a medium-severity memory corruption vulnerability in Siemens Jt2go, published on 9 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-28394 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-2020-28394/ (Markdown: https://insights.sbomify.com/CVE-2020-28394/index.md)","id":"CVE-2020-28394","markdown":"https://insights.sbomify.com/CVE-2020-28394/index.md","name":"CVE-2020-28394","record":{"aliases":["GHSA-prcr-frhq-gm4p"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Siemens visualization software","requires_auth":"low_privilege","summary":"Attackers can read process memory via crafted RAS files in Siemens JT2Go and Teamcenter Visualization due to improper input validation.","user_interaction":"not_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":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"A vulnerability has been identified in JT2Go (All versions \u003c V13.1.0.1), Teamcenter Visualization (All versions \u003c V13.1.0.1). Affected applications lack proper validation of user-supplied data when parsing of RAS files. This could result in a memory access past the end of an allocated buffer. An attacker could leverage this vulnerability to access data in the context of the current process. (ZDI-CAN-12283)","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-2020-28394","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"siemens:jt2go","products":["siemens:jt2go","siemens:teamcenter_visualization"],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Weak cryptography in SCALANCE X-200RNA switch family","id":"CVE-2020-28395"},"packages":[],"prev":{"headline":"Denial of service in SCALANCE XM-400, XR-500","id":"CVE-2020-28393"},"products":["JT2Go","Teamcenter Visualization"],"published":"2021-02-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Siemens"]},"summary":"Attackers can read process memory via crafted RAS files in Siemens JT2Go and Teamcenter Visualization due to improper input validation.","url":"https://insights.sbomify.com/CVE-2020-28394/"}