CVE-2024-43654
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 · uneditedImproper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Iocharger firmware for AC models allows OS Command Injection as root This issue affects all Iocharger AC EV charger models on a firmware version before 25010801. 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 confidenceOS Command Injection vulnerability in Iocharger AC EV charger firmware allows authenticated attackers to execute arbitrary commands as root by sending crafted HTTP requests to a specific binary. The vulnerability affects all AC model chargers on firmware versions before 25010801.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Iocharger AC model chargers on the networkLocate Iocharger AC EV charging stations by reviewing network device inventories, checking MAC vendor prefixes (if available), or accessing the device's web interface and noting the model name under System Info or About pages.Affected if The device is an Iocharger AC model charger.
-
Determine the installed firmware versionLog into the charger's web interface (typically via HTTP on the device's IP address) and navigate to the System Settings, Firmware Update, or About section. Alternatively, access the device via SSH or serial console and run the command 'version' or check /etc/version if accessible.Affected if The firmware version cannot be determined or is visible but shows a version number lower than 25010801.
-
Confirm the vulnerable binary is accessibleCheck if the web interface exposes an endpoint or functionality that interacts with the vulnerable binary. This may be visible in the URL paths of the admin interface (e.g., CGI scripts or API endpoints related to system commands, diagnostics, or configuration). Verify that the HTTP service is reachable from the network.Affected if The web interface is accessible and contains endpoints for system command execution, diagnostics, or configuration that map to the vulnerable binary.
-
Verify authentication is in useConfirm whether the device's admin interface requires authentication. Check if default credentials are in use or if the authentication mechanism can be bypassed. Review access control settings on the device or network segment.Affected if The device allows authenticated access to the command execution functionality, or authentication can be bypassed, allowing arbitrary HTTP requests to reach the vulnerable binary.
You are affected if you have an Iocharger AC EV charger running firmware versions before 25010801, with the web management interface accessible and the vulnerable command execution binary exposed.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Iocharger AC EV charger firmware to version 25010801 or later. Additionally, implement network segmentation to isolate EV charging infrastructure and limit the impact of potential compromise given the safety-critical nature of these devices.
Firmware version 25010801 or later
- Obtain the firmware version 25010801 or later from the official Iocharger vendor (iocharger.com or authorized distributors)
- Review Iocharger firmware upgrade documentation for AC model chargers
- Ensure the charger is in a safe state (not actively charging) before upgrading
- Upload and apply the firmware update through the Iocharger administrative interface or recommended upgrade procedure
- Verify the firmware upgrade was successful by checking the version number
- Confirm the command injection vulnerability is no longer present by testing the previously vulnerable functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43654 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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