CVE-2024-43657
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 model chargers before version 24120701. Likelihood: High. However, the attacker will need a (low privilege) account to gain access to the action.exe CGI binary and upload the crafted firmware file, or convince a user with such access to upload 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 confidenceIocharger AC model firmware before version 24120701 contains an OS command injection vulnerability in the action.exe CGI binary. An attacker with low-privilege account access can upload a crafted firmware file that is not properly sanitized, allowing execution of arbitrary OS commands with root privileges. This provides full compromise of the charging station with ability to modify files, services, and potentially pivot into connected networks.
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 device as Iocharger AC chargerAccess the device web interface or check the device model/firmware banner during startup. Look for Iocharger branding or model identification in the admin panel or device information page.Affected if The device is an Iocharger AC charger model running the vulnerable firmware upload functionality.
-
Check installed firmware versionLog into the device web interface and navigate to the firmware version or system information page. Alternatively, check the firmware file currently installed on the device via the admin panel or through a firmware dump if you have CLI access.Affected if The firmware version is lower than 24120701 (for example, 24110101, 24090102, etc.). Versions at or above 24120701 are not affected.
-
Verify web interface accessibilityAttempt to access the device IP address on port 80 or 443 from a network location. Check if the login page for the Iocharger web interface responds.Affected if The web interface is reachable from network locations where untrusted users could access it.
-
Confirm action.exe CGI binary existsAccess the device web interface and attempt to locate or reference the action.exe CGI binary. This is typically found in paths such as /cgi-bin/action.exe or similar CGI endpoints on the device.Affected if The action.exe CGI binary is present and accessible, indicating the vulnerable firmware upload functionality is available.
-
Check for low-privilege user accountsLog into the device admin panel and review the user account list. Identify if there are any user accounts with limited or non-administrative privileges configured on the device.Affected if There are authenticated user accounts with low-privilege access that could potentially upload firmware files through the action.exe endpoint.
You are affected if this is an Iocharger AC charger running firmware version earlier than 24120701, with the web interface and action.exe CGI binary accessible to authenticated low-privilege users.
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 charger firmware to version 24120701 or later to address the command injection vulnerability. Prioritize devices exposed to network access and implement network segmentation to limit exposure.
24120701 or later
- Identify the current firmware version of the Iocharger AC model charging station
- Download the latest firmware version 24120701 or later from the official Iocharger vendor
- Access the device's administrative web interface using valid credentials
- Navigate to the firmware update or system settings section
- Upload and apply the firmware file following the vendor's standard upgrade procedure
- Verify the firmware was successfully applied by checking the version in the system information
- Restart the device if required by the upgrade process
- Confirm the device is operational and the web interface is accessible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43657 — 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-43657 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