{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-38867 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-38867 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-38867 is a high-severity vulnerability in Siemens SIPROTEC 5 6MD84 (CP300), published on 9 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-38867 and fix it if it is affected.\n\nWhat it is: CVE-2024-38867 is a high-severity vulnerability in Siemens SIPROTEC 5 6MD84 (CP300), published on 9 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-38867 in the wild and no public exploit code.\n\nAffected product: Siemens SIPROTEC 5 6MD84 (CP300). 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-2024-38867/ (Markdown: https://insights.sbomify.com/CVE-2024-38867/index.md)","id":"CVE-2024-38867","markdown":"https://insights.sbomify.com/CVE-2024-38867/index.md","name":"CVE-2024-38867","record":{"aliases":["GHSA-h434-pjg4-qp56"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Siemens SIPROTEC 5","requires_auth":"none","summary":"Weak cryptographic implementation in Siemens SIPROTEC 5 devices allows attackers to bypass security controls, requiring firmware upgrades.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"siemens","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"A vulnerability has been identified in SIPROTEC 5 6MD84 (CP300) (All versions \u003c V9.64), SIPROTEC 5 6MD85 (CP200) (All versions), SIPROTEC 5 6MD85 (CP300) (All versions \u003c V9.64), SIPROTEC 5 6MD86 (CP200) (All versions), SIPROTEC 5 6MD86 (CP300) (All versions \u003c V9.64), SIPROTEC 5 6MD89 (CP300) (All versions \u003c V9.64), SIPROTEC 5 6MU85 (CP300) (All versions \u003c V9.64), SIPROTEC 5 7KE85 (CP200) (All versions), SIPROTEC 5 7KE85 (CP300) (All versions \u003c V9.64), SIPROTEC 5 7SA82 (CP100) (All versions \u003c V8.90), SIPROTEC 5 7SA82 (CP150) (All versions \u003c V9.65), SIPROTEC 5 7SA84 (CP200) (All versions), SIPROTEC 5 7SA86 (CP200) (All versions), SIPROTEC 5 7SA86 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7SA87 (CP200) (All versions), SIPROTEC 5 7SA87 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7SD82 (CP100) (All versions \u003c V8.90), SIPROTEC 5 7SD82 (CP150) (All versions \u003c V9.65), SIPROTEC 5 7SD84 (CP200) (All versions), SIPROTEC 5 7SD86 (CP200) (All versions), SIPROTEC 5 7SD86 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7SD87 (CP200) (All versions), SIPROTEC 5 7SD87 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7SJ81 (CP100) (All versions \u003c V8.89), SIPROTEC 5 7SJ81 (CP150) (All versions \u003c V9.65), SIPROTEC 5 7SJ82 (CP100) (All versions \u003c V8.89), SIPROTEC 5 7SJ82 (CP150) (All versions \u003c V9.65), SIPROTEC 5 7SJ85 (CP200) (All versions), SIPROTEC 5 7SJ85 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7SJ86 (CP200) (All versions), SIPROTEC 5 7SJ86 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7SK82 (CP100) (All versions \u003c V8.89), SIPROTEC 5 7SK82 (CP150) (All versions \u003c V9.65), SIPROTEC 5 7SK85 (CP200) (All versions), SIPROTEC 5 7SK85 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7SL82 (CP100) (All versions \u003c V8.90), SIPROTEC 5 7SL82 (CP150) (All versions \u003c V9.65), SIPROTEC 5 7SL86 (CP200) (All versions), SIPROTEC 5 7SL86 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7SL87 (CP200) (All versions), SIPROTEC 5 7SL87 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7SS85 (CP200) (All versions), SIPROTEC 5 7SS85 (CP300) (All versions \u003c V9.64), SIPROTEC 5 7ST85 (CP200) (All versions), SIPROTEC 5 7ST85 (CP300) (All versions \u003c V9.64), SIPROTEC 5 7ST86 (CP300) (All versions \u003c V9.64), SIPROTEC 5 7SX82 (CP150) (All versions \u003c V9.65), SIPROTEC 5 7SX85 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7UM85 (CP300) (All versions \u003c V9.64), SIPROTEC 5 7UT82 (CP100) (All versions \u003c V8.90), SIPROTEC 5 7UT82 (CP150) (All versions \u003c V9.65), SIPROTEC 5 7UT85 (CP200) (All versions), SIPROTEC 5 7UT85 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7UT86 (CP200) (All versions), SIPROTEC 5 7UT86 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7UT87 (CP200) (All versions), SIPROTEC 5 7UT87 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7VE85 (CP300) (All versions \u003c V9.64), SIPROTEC 5 7VK87 (CP200) (All versions), SIPROTEC 5 7VK87 (CP300) (All versions \u003c V9.65), SIPROTEC 5 7VU85 (CP300) (All versions \u003c V9.64), SIPROTEC 5 Communication Module ETH-BA-2EL (Rev.1) (All versions \u003c V9.62 installed on CP150 and CP300 devices), SIPROTEC 5 Communication Module ETH-BA-2EL (Rev.1) (All versions installed on CP200 devices), SIPROTEC 5 Communication Module ETH-BA-2EL (Rev.1) (All versions \u003c V8.89 installed on CP100 devices), SIPROTEC 5 Communication Module ETH-BB-2FO (Rev. 1) (All versions installed on CP200 devices), SIPROTEC 5 Communication Module ETH-BB-2FO (Rev. 1) (All versions \u003c V9.62 installed on CP150 and CP300 devices), SIPROTEC 5 Communication Module ETH-BB-2FO (Rev. 1) (All versions \u003c V8.89 installed on CP100 devices), SIPROTEC 5 Communication Module ETH-BD-2FO (All versions \u003c V9.62), SIPROTEC 5 Compact 7SX800 (CP050) (All versions \u003c V9.64). The affected devices are supporting weak ciphers on several ports (443/tcp for web, 4443/tcp for DIGSI 5 and configurable port for syslog over TLS). \r\nThis could allow an unauthorized attacker in a man-in-the-middle position to decrypt any data passed over to and from those ports.","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":"Weak cryptography in SIPROTEC 5 6MD84 (CP300)","id":"CVE-2024-38867","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Incorrect Authorization","id":"CVE-2024-38868"},"packages":[],"prev":{"headline":"Livestatus Injection in dynmaps","id":"CVE-2024-38866"},"products":["SIPROTEC 5 6MD84 (CP300)","SIPROTEC 5 6MD85 (CP200)","SIPROTEC 5 6MD85 (CP300)","SIPROTEC 5 6MD86 (CP200)","SIPROTEC 5 6MD86 (CP300)","SIPROTEC 5 6MD89 (CP300)","SIPROTEC 5 6MU85 (CP300)","SIPROTEC 5 7KE85 (CP200)","SIPROTEC 5 7KE85 (CP300)","SIPROTEC 5 7SA82 (CP100)","SIPROTEC 5 7SA82 (CP150)","SIPROTEC 5 7SA84 (CP200)","SIPROTEC 5 7SA86 (CP200)","SIPROTEC 5 7SA86 (CP300)","SIPROTEC 5 7SA87 (CP200)","SIPROTEC 5 7SA87 (CP300)","SIPROTEC 5 7SD82 (CP100)","SIPROTEC 5 7SD82 (CP150)","SIPROTEC 5 7SD84 (CP200)","SIPROTEC 5 7SD86 (CP200)","SIPROTEC 5 7SD86 (CP300)","SIPROTEC 5 7SD87 (CP200)","SIPROTEC 5 7SD87 (CP300)","SIPROTEC 5 7SJ81 (CP100)","SIPROTEC 5 7SJ81 (CP150)","SIPROTEC 5 7SJ82 (CP100)","SIPROTEC 5 7SJ82 (CP150)","SIPROTEC 5 7SJ85 (CP200)","SIPROTEC 5 7SJ85 (CP300)","SIPROTEC 5 7SJ86 (CP200)","SIPROTEC 5 7SJ86 (CP300)","SIPROTEC 5 7SK82 (CP100)","SIPROTEC 5 7SK82 (CP150)","SIPROTEC 5 7SK85 (CP200)","SIPROTEC 5 7SK85 (CP300)","SIPROTEC 5 7SL82 (CP100)","SIPROTEC 5 7SL82 (CP150)","SIPROTEC 5 7SL86 (CP200)","SIPROTEC 5 7SL86 (CP300)","SIPROTEC 5 7SL87 (CP200)","SIPROTEC 5 7SL87 (CP300)","SIPROTEC 5 7SS85 (CP200)","SIPROTEC 5 7SS85 (CP300)","SIPROTEC 5 7ST85 (CP200)","SIPROTEC 5 7ST85 (CP300)","SIPROTEC 5 7ST86 (CP300)","SIPROTEC 5 7SX82 (CP150)","SIPROTEC 5 7SX85 (CP300)","SIPROTEC 5 7UM85 (CP300)","SIPROTEC 5 7UT82 (CP100)","SIPROTEC 5 7UT82 (CP150)","SIPROTEC 5 7UT85 (CP200)","SIPROTEC 5 7UT85 (CP300)","SIPROTEC 5 7UT86 (CP200)","SIPROTEC 5 7UT86 (CP300)","SIPROTEC 5 7UT87 (CP200)","SIPROTEC 5 7UT87 (CP300)","SIPROTEC 5 7VE85 (CP300)","SIPROTEC 5 7VK87 (CP200)","SIPROTEC 5 7VK87 (CP300)","SIPROTEC 5 7VU85 (CP300)","SIPROTEC 5 Communication Module ETH-BA-2EL (Rev.1)","SIPROTEC 5 Communication Module ETH-BB-2FO (Rev. 1)","SIPROTEC 5 Communication Module ETH-BD-2FO","SIPROTEC 5 Compact 7SX800 (CP050)"],"published":"2024-07-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-11-11","vendors":["Siemens"]},"summary":"Weak cryptographic implementation in Siemens SIPROTEC 5 devices allows attackers to bypass security controls, requiring firmware upgrades.","url":"https://insights.sbomify.com/CVE-2024-38867/"}