CVE-2024-43652
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: 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.
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 confidenceA command injection vulnerability in Iocharger AC charger firmware allows attackers with low-privilege account access to inject OS commands that execute with root privileges. The vulnerability exists in a specific binary that, while not directly exposed by the web interface, can be reached through crafted HTTP requests.
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 firmware versionAccess the device admin interface or check system information page for the current firmware build number. On most network devices, this is found under System, Maintenance, or About sections.Affected if The firmware version is lower than 24120701 (e.g., 2409xxx or earlier builds).
-
Determine if web/API service is exposedVerify whether the Iocharger device HTTP service is accessible from untrusted networks. Check network configuration or firewall rules for port 80/443 or custom HTTP ports.Affected if The HTTP interface is reachable from network segments where untrusted users exist.
-
Review user account privilegesList all user accounts configured on the Iocharger device. Identify whether any accounts have only limited or low-privilege access rather than full administrative rights.Affected if Low-privilege user accounts exist on the device, as these accounts can be used as an attack vector.
-
Check for suspicious HTTP endpoints or behaviorReview web server logs or network traffic captures for unusual or crafted HTTP request patterns targeting non-standard endpoints. Look for requests containing shell metacharacters.Affected if Evidence of anomalous HTTP requests or unexpected binaries being invoked through the web interface exists.
A user is affected if their Iocharger AC firmware version is below 24120701 AND the device HTTP interface is accessible to 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 model firmware to version 24120701 or later to remediate this command injection vulnerability.
24120701
- Check the current firmware version of the Iocharger AC model charger
- Download firmware version 24120701 or later from the official Iocharger vendor (iocharger.com)
- Follow the vendor's documented firmware update procedure to apply the new version
- Verify the upgrade was successful by confirming the firmware version is 24120701 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43652 — 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-43652 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