{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47943 exists.","fix":"No fix has been published for CVE-2024-47943 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-47943 is a critical vulnerability in RITTAL GmbH \u0026 Co. KG IoT Interface \u0026 CMC III Processing Unit, published on 15 Oct 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-47943 and fix it if it is affected.\n\nWhat it is: CVE-2024-47943 is a critical vulnerability in RITTAL GmbH \u0026 Co. KG IoT Interface \u0026 CMC III Processing Unit, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47943 exists.\n\nAffected product: RITTAL GmbH \u0026 Co. KG IoT Interface \u0026 CMC III Processing Unit. 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-47943/ (Markdown: https://insights.sbomify.com/CVE-2024-47943/index.md)","id":"CVE-2024-47943","markdown":"https://insights.sbomify.com/CVE-2024-47943/index.md","name":"CVE-2024-47943","record":{"aliases":["GHSA-3ggr-5p57-2xgh"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"IoT Interface \u0026 CMC III","requires_auth":"none","summary":"Attackers can execute arbitrary code on Rittal IoT devices by crafting malicious firmware patches using a hard-coded HMAC key.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SEC-VLab","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The firmware upgrade function in the admin web interface of the Rittal IoT Interface \u0026 CMC III Processing Unit devices checks if \nthe patch files are signed before executing the containing run.sh \nscript. The signing process is kind of an HMAC with a long string as key\n which is hard-coded in the firmware and is freely available for \ndownload. This allows crafting malicious \"signed\" .patch files in order \nto compromise the device and execute arbitrary code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Improper signature verification of firmware upgrade files","id":"CVE-2024-47943","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Protection Mechanism for Alternate Hardware Interface","id":"CVE-2024-47944"},"packages":[],"prev":{"headline":"Other in Solid Edge SE2024","id":"CVE-2024-47942"},"products":["IoT Interface \u0026 CMC III Processing Unit"],"published":"2024-10-15","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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-03","vendors":["RITTAL GmbH \u0026 Co. KG"]},"summary":"Attackers can execute arbitrary code on Rittal IoT devices by crafting malicious firmware patches using a hard-coded HMAC key.","url":"https://insights.sbomify.com/CVE-2024-47943/"}