CVE-2024-43651
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 allows OS Command Injection as root This issue affects Iocharger firmware for AC models before version 241207101 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 connection serving the web interface is vulnerable (AV:N) and there are no additional measures to circumvent (AC:L) nor does the attack require special conditions to be present (AT:N). The attack requires authentication, but the level does not matter (PR:L), nor is user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H) and a compromised device can be used to potentially "pivot" into a network that should nopt be reachable (SC:L/SI:L/SA:H). Because this is an EV charger handing significant power, there is a potential safety impact (S:P). THe attack can be autometed (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 confidenceIocharger AC firmware before version 241207101 contains a command injection vulnerability in a binary that can be accessed via crafted HTTP requests. An authenticated attacker can inject OS commands that execute with root privileges, achieving full compromise of the charging station.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is Iocharger ACIdentify the charging station model through device documentation, web interface banner, or physical labeling. Verify it is an Iocharger AC series device.Affected if The device is not an Iocharger AC product, then this CVE does not apply.
-
Check firmware versionAccess the device web interface or administrative console and locate the firmware version information, typically found in Settings, System Info, or About pages. Compare the installed version to 241207101.Affected if The installed firmware version is lower than 241207101 (for example, 241206xxx or earlier).
-
Verify HTTP interface accessibilityAttempt to reach the device web interface over HTTP/HTTPS from a trusted network location. Confirm the management web portal is reachable.Affected if The web interface is accessible from untrusted networks, increasing exposure to authenticated attackers.
-
Review authentication configurationCheck the list of user accounts configured on the device. Determine if default or weak credentials are in use, and verify whether the account has any privilege level.Affected if Any valid credentials exist on the device (even low-privilege accounts), as the vulnerability can be exploited with authenticated access.
A defender is affected if they operate an Iocharger AC charging station running firmware version lower than 241207101 with the web interface accessible using any valid credentials.
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 firmware to version 241207101 or later. Additionally, review and restrict access to accounts with any privilege level, as even low-privilege credentials can enable exploitation.
Firmware version 241207101 or later
- 1. Identify the Iocharger AC model charging station on the network
- 2. Check the current firmware version through the device's web interface or administrative console
- 3. Obtain firmware version 241207101 or later from the official Iocharger vendor (via their support portal or official channels)
- 4. Following the vendor's documented firmware upgrade procedure, upload and apply the new firmware to the device
- 5. After upgrade, verify the firmware version has been successfully updated to 241207101 or later
- 6. Confirm the command injection vulnerability is remediated by attempting the attack vector with valid low-privilege credentials
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-43651 — 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-43651 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