{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-36360 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36360 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36360 is a high-severity vulnerability in Siemens LOGO! 8 BM (incl. SIPLUS variants), published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36360 and fix it if it is affected.\n\nWhat it is: CVE-2022-36360 is a high-severity vulnerability in Siemens LOGO! 8 BM (incl. SIPLUS variants), published on 11 Oct 2022. 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-2022-36360 in the wild and no public exploit code.\n\nAffected product: Siemens LOGO! 8 BM (incl. SIPLUS variants). 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-36360/ (Markdown: https://insights.sbomify.com/CVE-2022-36360/index.md)","id":"CVE-2022-36360","markdown":"https://insights.sbomify.com/CVE-2022-36360/index.md","name":"CVE-2022-36360","record":{"aliases":["GHSA-qqx5-8972-3h6c"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Siemens LOGO! 8 BM","requires_auth":"none","summary":"Attackers can flash malicious firmware to Siemens LOGO! 8 BM devices due to missing authenticity checks and weak integrity verification.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"siemens","cpe":[{"product":"logo\\!8_bm_fs-05_firmware","vendor":"siemens"},{"product":"logo\\!_8_bm_firmware","vendor":"siemens"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions \u003c V8.3). Affected devices load firmware updates without checking the authenticity. Furthermore the integrity of the unencrypted firmware is only verified by a non-cryptographic method. This could allow an attacker to manipulate a firmware update and flash it to the device.","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":"Security feature bypass in LOGO! 8 BM (incl. SIPLUS variants)","id":"CVE-2022-36360","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in LOGO! 12/24RCE","id":"CVE-2022-36361"},"packages":[],"prev":{"headline":"Django vulnerable to Reflected File Download attack","id":"CVE-2022-36359"},"products":["LOGO! 8 BM (incl. SIPLUS variants)"],"published":"2022-10-11","related":[{"cvss_score":9.8,"headline":"Memory corruption in LOGO! 12/24RCE","id":"CVE-2022-36361","kev_date_added":null,"published":"2022-10-11"},{"cvss_score":7.5,"headline":"Missing authorization in LOGO! 12/24RCE","id":"CVE-2022-36362","kev_date_added":null,"published":"2022-10-11"},{"cvss_score":7.5,"headline":"Information disclosure in LOGO! 8 BM (incl. SIPLUS variants)","id":"CVE-2017-12734","kev_date_added":null,"published":"2017-08-30"},{"cvss_score":5.3,"headline":"Information disclosure in LOGO! 12/24RCE","id":"CVE-2022-36363","kev_date_added":null,"published":"2022-10-11"}],"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-03","vendors":["Siemens"]},"summary":"Attackers can flash malicious firmware to Siemens LOGO! 8 BM devices due to missing authenticity checks and weak integrity verification.","url":"https://insights.sbomify.com/CVE-2022-36360/"}