Root command execution via embedded firmware script
Published Jan 9, 2025 · Updated Mar 11, 2025
OS command injection in Iocharger firmware for AC model chargers before 2024120701 allows remote authenticated users to execute code as root. The firmware-update path accepts a crafted firmware file and executes an embedded shell script while action.exe processes the upload. Access to the web UI with any account, or interaction by a user who has such access, is required; successful exploitation grants full control of charger files and services.
Summary
What happened
OS command injection in Iocharger firmware for AC model chargers before 2024120701 allows remote authenticated users to execute code as root. The firmware-update path accepts a crafted firmware file and executes an embedded shell script while action.exe processes the upload. Access to the web UI with any account, or interaction by a user who has such access, is required; successful exploitation grants full control of charger files and services.
The record
- CVE
- CVE-2024-43657
- Published
- Jan 9, 2025
- Updated
- Mar 11, 2025
- Vendor
- Iocharger
- Product
- Iocharger Firmware for AC Models
- Classifications
- CWE-434, CWE-78, CAPEC-88, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2025CVE publishedPublication date reported by the CVE source.
- Mar 11, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2024120701
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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