# CVE-2024-43648: Authenticated command injection via .exe parameter > Authenticated attackers can execute arbitrary commands as root on Iocharger EV charging stations via a vulnerable parameter, leading to full system compromise. - **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:H/S:P/AU:Y`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 9 Jan 2025 - **Updated:** 11 Mar 2025 - **Also known as:** GHSA-r3r4-jc6c-965m ## What is CVE-2024-43648? CVE-2024-43648 is a critical command injection vulnerability in Iocharger firmware for AC models, published on 9 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Command injection in the parameter of a .exe request leads to remote code execution as the root user. This issue affects Iocharger firmware for AC models before version 24120701. Likelihood: Moderate – This action is not a common place for command injection vulnerabilities to occur. Thus, an attacker will likely only be able to find this vulnerability by reverse-engineering the firmware or trying it on all fields. The attacker will also need a (low privilege) account to gain access to the binary, or convince a user with such access to execute a payload. Impact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete files and services. CVSS clarification. The attack can be executed over any network connection the station is listening to and serves the web interface (AV:N), and there are no additional security measure sin place that need to be circumvented (AC:L), the attack does not rely on preconditions (AT:N). The attack does require authentication, but the level of authentication is irrelevant (PR:L), it does not require user interaction (UI:N). If is a full system compromise, potentially fully compromising confidentiality, integrity and availability of the devicer (VC:H/VI:H/VA:H).  A compromised charger can be used to "pivot" onto networks that should otherwise be closed, cause a low confidentiality and interity impact on subsequent systems. (SC:L/SI:L/SA:H). Because this device is an EV charger handing significant amounts of power, we suspect this vulnerability can have a safety impact (S:P). The attack can be automated (AU:Y). Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-250 (Execution with Unnecessary Privileges) ## Which versions are affected by CVE-2024-43648? ## How do I fix CVE-2024-43648? No fix has been published for CVE-2024-43648 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-43648 being exploited? There is no known exploitation of CVE-2024-43648 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-43648 and fix it if it is affected. What it is: CVE-2024-43648 is a critical command injection vulnerability in Iocharger firmware for AC models, published on 9 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-43648 in the wild and no public exploit code. Affected product: Iocharger firmware for AC models. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-43648/ (Markdown: https://insights.sbomify.com/CVE-2024-43648/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-43648 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-43648 - OSV: https://osv.dev/vulnerability/CVE-2024-43648 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-43648/ Summaries are generated and may contain mistakes; the official description above is the record.