Physical code execution via unauthenticated USB firmware
Published Oct 15, 2024 · Updated Nov 3, 2025
Code execution in Rittal IoT Interface and CMC III Processing Unit before 6.21.00.2 allows physically proximate attackers to run code via USB. A device-side script scans newly attached USB sticks or SD cards and sends any .patch file it finds through signature verification for execution. Exploitation requires physical media containing a signed patch; when combined with the separate signature-forgery flaw, attacker code runs with root privileges.
Summary
What happened
Code execution in Rittal IoT Interface and CMC III Processing Unit before 6.21.00.2 allows physically proximate attackers to run code via USB. A device-side script scans newly attached USB sticks or SD cards and sends any .patch file it finds through signature verification for execution. Exploitation requires physical media containing a signed patch; when combined with the separate signature-forgery flaw, attacker code runs with root privileges.
The record
- CVE
- CVE-2024-47944
- Published
- Oct 15, 2024
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1299, CAPEC-186, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- create_signed_firmware.pyfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo