{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-41224 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-41224 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-41224 is a high-severity vulnerability in Siemens RUGGEDCOM RMC8388 V5.X, published on 8 Jul 2025. 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-2025-41224 and fix it if it is affected.\n\nWhat it is: CVE-2025-41224 is a high-severity vulnerability in Siemens RUGGEDCOM RMC8388 V5.X, published on 8 Jul 2025. 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-2025-41224 in the wild and no public exploit code.\n\nAffected product: Siemens RUGGEDCOM RMC8388 V5.X. 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-2025-41224/ (Markdown: https://insights.sbomify.com/CVE-2025-41224/index.md)","id":"CVE-2025-41224","markdown":"https://insights.sbomify.com/CVE-2025-41224/index.md","name":"CVE-2025-41224","record":{"aliases":["GHSA-fg6g-24v3-5276"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Siemens RUGGEDCOM switch","requires_auth":"none","summary":"Attackers can bypass interface access restrictions on Siemens RUGGEDCOM devices by changing configurations without rebooting, requiring network access and credentials.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"siemens","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"A vulnerability has been identified in RUGGEDCOM RMC8388 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RMC8388NC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS416NCv2 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS416PNCv2 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS416Pv2 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS416v2 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS900 (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS900G (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS900GNC(32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS900NC(32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2100 (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2100NC(32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2100P (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2100PNC (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2288 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2288NC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2300 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2300NC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2300P V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2300PNC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2488 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2488NC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG907R (All versions \u003c V5.10.0), RUGGEDCOM RSG908C (All versions \u003c V5.10.0), RUGGEDCOM RSG909R (All versions \u003c V5.10.0), RUGGEDCOM RSG910C (All versions \u003c V5.10.0), RUGGEDCOM RSG920P V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG920PNC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSL910 (All versions \u003c V5.10.0), RUGGEDCOM RSL910NC (All versions \u003c V5.10.0), RUGGEDCOM RST2228 (All versions \u003c V5.10.0), RUGGEDCOM RST2228P (All versions \u003c V5.10.0), RUGGEDCOM RST916C (All versions \u003c V5.10.0), RUGGEDCOM RST916P (All versions \u003c V5.10.0). The affected products do not properly enforce interface access restrictions when changing from management to non-management interface configurations until a system reboot occurs, despite configuration being saved. This could allow an attacker with network access and credentials to gain access to device through non-management and maintain SSH access to the device until reboot.","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 RUGGEDCOM RMC8388 V5.X","id":"CVE-2025-41224","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"VMware vCenter Server authenticated command-execution vulnerability","id":"CVE-2025-41225"},"packages":[],"prev":{"headline":"Weak cryptography in RUGGEDCOM M2100","id":"CVE-2025-41223"},"products":["RUGGEDCOM RMC8388 V5.X","RUGGEDCOM RMC8388NC V5.X","RUGGEDCOM RS416NCv2 V5.X","RUGGEDCOM RS416PNCv2 V5.X","RUGGEDCOM RS416Pv2 V5.X","RUGGEDCOM RS416v2 V5.X","RUGGEDCOM RS900 (32M) V5.X","RUGGEDCOM RS900G (32M) V5.X","RUGGEDCOM RS900GNC(32M) V5.X","RUGGEDCOM RS900NC(32M) V5.X","RUGGEDCOM RSG2100 (32M) V5.X","RUGGEDCOM RSG2100NC(32M) V5.X","RUGGEDCOM RSG2100P (32M) V5.X","RUGGEDCOM RSG2100PNC (32M) V5.X","RUGGEDCOM RSG2288 V5.X","RUGGEDCOM RSG2288NC V5.X","RUGGEDCOM RSG2300 V5.X","RUGGEDCOM RSG2300NC V5.X","RUGGEDCOM RSG2300P V5.X","RUGGEDCOM RSG2300PNC V5.X","RUGGEDCOM RSG2488 V5.X","RUGGEDCOM RSG2488NC V5.X","RUGGEDCOM RSG907R","RUGGEDCOM RSG908C","RUGGEDCOM RSG909R","RUGGEDCOM RSG910C","RUGGEDCOM RSG920P V5.X","RUGGEDCOM RSG920PNC V5.X","RUGGEDCOM RSL910","RUGGEDCOM RSL910NC","RUGGEDCOM RST2228","RUGGEDCOM RST2228P","RUGGEDCOM RST916C","RUGGEDCOM RST916P"],"published":"2025-07-08","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":"total"},"state":"PUBLISHED","updated":"2025-07-08","vendors":["Siemens"]},"summary":"Attackers can bypass interface access restrictions on Siemens RUGGEDCOM devices by changing configurations without rebooting, requiring network access and credentials.","url":"https://insights.sbomify.com/CVE-2025-41224/"}