CVE-2024-43650
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 firmware versions before 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: The attack can be executed over any network connection serving the web interface (AV:N). There are no additional measures that need to be circumvented (AC:L) or attack preconditions (AT:N). THe attack is privileged, but the level does not matter (PR:L) and does not require user interaction (UI:N). Attack leads to full system compromised (VC:H/VI:H/VA:H) and compromised devices can be used to "pivot" to other networks that should be unreachable (SC:L/SI:L/SA:H). Because this an EV charger using high power, there is a potential safety impact (S:P). The 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 confidenceIocharger AC charging station firmware contains a command injection vulnerability in a binary that can be reached via crafted HTTP requests. An authenticated attacker with low-privilege access can inject arbitrary OS commands that execute with root privileges, achieving full system compromise.
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.
-
Identify Iocharger AC device on networkScan the network for devices with Iocharger HTTP service (typically port 80/443) or identify Iocharger MAC/vendor OUIs. Check DHCP logs or network scans for Iocharger charging station IP addresses.Affected if An Iocharger AC charging station is present on the network.
-
Determine firmware versionAccess the device web interface and navigate to System Settings or Device Info page. Look for a firmware/build version field. Alternatively, check the HTTP response headers or API endpoints for version information.Affected if Firmware version is present and is earlier than 24120701, or version cannot be determined but device is exposed.
-
Verify web interface accessibilityCheck if the device HTTP/HTTPS port is reachable from external networks or the internet. Review firewall rules, NAT configurations, and port forwarding settings for the charging station IP.Affected if The web interface is accessible from untrusted networks (not just internal LAN).
-
Check authentication configurationExamine the user accounts configured on the device through the web interface. Verify if low-privilege user accounts exist and whether default credentials are in use.Affected if Low-privilege user accounts are enabled or default credentials remain unchanged.
The environment is affected if an Iocharger AC charging station is present with firmware version earlier than 24120701 and its web interface is network-accessible, allowing authenticated command injection.
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 · scopedUpdate Iocharger AC model firmware to version 24120701 or later. Until the vendor update is available, restrict network access to the charging station web interface and disable remote access.
Firmware version 24120701
- Identify the current Iocharger AC model firmware version through the web interface or administrative console
- Navigate to the official Iocharger support page (iocharger.com) or contact Iocharger directly to obtain firmware version 24120701 or later
- Follow Iocharger's official firmware update procedure, typically involving uploading the firmware file through the web interface or a dedicated update tool
- After updating, verify the firmware version has been successfully upgraded to 24120701 or later
- Confirm the command injection vulnerability is no longer present by reviewing release notes or consulting Iocharger documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43650 — 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-43650 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