dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-43649

HIGH · 8.8 CVSS v3.1 Published 2025-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authenticated command injection in the filename of a <redacted>.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 <redacted> fields. The attacker will also need a (low privilege) account to gain access to the <redacted> 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: This attack can be performed over any network conenction serving the web interfacr (AV:N), and there are not additional mitigating measures that need to be circumvented (AC:L) or other prerequisites (AT:N). The attack does require privileges, but the level does not matter (PR:L), there is no user interaction required (UI:N). The attack leeds to a full compromised of the charger (VC:H/VI:H/VA:H) and a compromised charger can be used to "pivot" to networks that should normally not be reachable (SC:L/SI:L/SA:H). Because this is an EV chargers with significant pwoer, there is a potential safety imp0act (S:P). THis attack can be automated (AU:Y).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated command injection vulnerability in Iocharger AC firmware allows low-privilege users to inject OS commands through the filename parameter of a .exe request. The injected commands execute with root privileges, enabling full device compromise. The vulnerability exists in firmware versions prior to 24120701.

MitigationUpdate Iocharger AC firmware to version 24120701 or later to remediate this vulnerability. Apply input validation and sanitization on all filename parameters in executable requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Iocharger AC device
    Identify the device model through the web interface header, system info page, or physical labeling. Look for Iocharger AC or EV charger branding.
    Affected if Device is not an Iocharger AC product (not vulnerable to this specific CVE)
  2. Check firmware version
    Access the device web interface and navigate to the system information or firmware version page. Note the exact firmware build number displayed.
    Affected if Firmware version is earlier than 24120701 (versions 24120701 and later are patched)
  3. Verify web interface accessibility
    Determine if the device web interface is reachable from untrusted networks. Check router port forwarding rules, VPN status, or firewall policies that expose the device IP on ports 80/443.
    Affected if Web interface is directly exposed to the internet or untrusted LAN segments (increases attack surface for authenticated exploitation)
  4. Review user account inventory
    Check the user management or account settings page in the web interface to list all configured users, including any low-privilege or read-only accounts.
    Affected if Any user account exists (even low-privilege accounts can exploit this vulnerability to gain root RCE)

The environment is affected if the device is an Iocharger AC with firmware version before 24120701 and has any user account configured with network access to the web interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Iocharger AC firmware to version 24120701 or later to remediate this vulnerability. Apply input validation and sanitization on all filename parameters in executable requests.

Recommended fix High confidence

24120701

  1. Obtain the Iocharger firmware version 24120701 or later from the official Iocharger source (iocharger.com)
  2. Log into the Iocharger web interface with administrator credentials
  3. Navigate to the firmware update or system settings section
  4. Upload and apply the firmware version 24120701
  5. Verify the upgrade was successful by checking the firmware version in the device settings
  6. Confirm the device is functioning normally after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43649 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43649 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data