dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-43655

CRITICAL · 9.3 CVSS v4.0 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 →
99/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 attacker will first need to find the name of the script, and needs a (low privilege) account to gain access to the script, or convince a user with such access to execute a request to it. Impact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles 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

Command injection vulnerability in Iocharger AC model firmware before version 24120701 allows authenticated attackers to execute arbitrary OS commands with root privileges through the web interface. The vulnerability requires a low-privilege account but the authentication level does not matter for exploitation.

MitigationUpdate Iocharger AC model firmware to version 24120701 or later. If immediate update is not possible, restrict network access to the charging station web interface and disable remote management features.

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
Authentication
Y
User interaction
None
Scope
P

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:X/V:X/RE:X/U:X

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. Identify the device model
    Access the device web interface or check the device label/marketing materials to confirm it is an Iocharger AC model charging station
    Affected if The device is not an Iocharger AC model (this CVE does not apply)
  2. Check firmware version via web interface
    Log into the device web interface and navigate to the System Settings, About, or Status page to view the installed firmware version
    Affected if The displayed firmware version is lower than 24120701 (for example, 24110101 or any earlier date code)
  3. Check firmware version via API or diagnostic interface
    If the web interface is not accessible, query the device API or use the manufacturer diagnostic tool to retrieve the firmware build date
    Affected if The firmware build date or version is earlier than 24120701
  4. Verify web interface is enabled
    Confirm that the device web interface is accessible on the expected IP address or hostname
    Affected if The web interface is active and reachable on the network
  5. Check remote management status
    If accessible in the settings, verify whether remote management, cloud connectivity, or external access features are enabled on the device
    Affected if Remote management or cloud features are enabled, increasing the attack surface

The environment is affected if the device is an Iocharger AC model running firmware version lower than 24120701 and the web interface is accessible.

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 model firmware to version 24120701 or later. If immediate update is not possible, restrict network access to the charging station web interface and disable remote management features.

Recommended fix High confidence

Firmware version 24120701 or later

  1. Identify the current Iocharger AC model firmware version via the web interface or administrative panel
  2. Download the fixed firmware version 24120701 or later from the official Iocharger vendor (iocharger.com)
  3. Review the vendor's firmware upgrade documentation and ensure all prerequisites are met
  4. Create a backup of current device configuration if possible
  5. Upload and install the firmware update via the device's administrative interface
  6. After installation, verify the firmware version has been updated to 24120701 or later
  7. Verify that the command injection vulnerability is no longer present
  8. Ensure the device is properly secured post-update (change default credentials, review access controls)
Caveat Ensure to back up device configuration before upgrading; test the new firmware in a staging environment if possible before production deployment

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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