dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-43653

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
Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability  allows OS Command Injection as root This issue affects Iocharger firmware for AC model chargers before version 24120701. Likelihood: Moderate – The <redacted> binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. 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 crafted HTTP request. 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: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (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

Iocharger AC model firmware before version 24120701 contains an OS command injection vulnerability in an undocumented binary. An authenticated attacker with low-privilege access can inject arbitrary OS commands via crafted HTTP requests and execute them with root privileges, achieving full compromise of the charging station.

MitigationUpgrade Iocharger AC charger firmware to version 24120701 or later to remediate this vulnerability. Prioritize devices exposed to untrusted networks given the critical impact and potential for network pivoting.

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 device model is Iocharger AC
    Access the charger web interface or physical device label to identify the exact model. Iocharger AC is the affected product line.
    Affected if Device is not an Iocharger AC model charger
  2. Check installed firmware version
    Log into the web interface and navigate to System Settings, Device Info, or About page to view the firmware version number. Compare against the fixed version 24120701.
    Affected if Firmware version is below 24120701 (any version older than December 7, 2024)
  3. Verify web interface accessibility
    Determine if the charger web management interface is exposed to untrusted networks or the internet. Check router/firewall port forwarding rules and network segmentation.
    Affected if Web interface is accessible from untrusted network segments or directly internet-facing
  4. Audit user accounts
    Access the user management section of the web interface to list all accounts. Note if any accounts with limited or guest-level privileges exist.
    Affected if Low-privilege or guest user accounts are configured on the device

Device is affected if it is an Iocharger AC model with firmware version lower than 24120701 and has low-privilege accounts or exposed web interface, allowing authenticated command injection.

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

Upgrade Iocharger AC charger firmware to version 24120701 or later to remediate this vulnerability. Prioritize devices exposed to untrusted networks given the critical impact and potential for network pivoting.

Recommended fix High confidence

24120701

  1. Obtain the Iocharger firmware version 24120701 or later from the official vendor (iocharger.com)
  2. Verify the firmware integrity using checksums provided by the vendor
  3. Access the Iocharger AC charger administration interface
  4. Navigate to the firmware update section
  5. Upload and install firmware version 24120701 or later
  6. Verify the firmware was applied successfully
  7. Confirm the web interface 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 / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43653 — 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-43653 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