dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2024-43663

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
There are many buffer overflow vulnerabilities present in several CGI binaries of the charging station.This issue affects Iocharger firmware for AC model chargers beforeversion 24120701. Likelihood: High – Given the prevalence of these buffer overflows, and the clear error message of the web server, an attacker is very likely to be able to find these vulnerabilities. Impact: Low – Usually, overflowing one of these buffers just causes a segmentation fault of the CGI binary, which causes the web server to return a 502 Bad Gateway error. However the webserver itself is not affected, and no DoS can be achieved. Abusing these buffer overflows in a meaningful way requires highly technical knowledge, especially since ASLR also seems to be enabled on the charging station. However, a skilled attacker might be able to use one of these buffer overflows to obtain remote code execution. CVSS clarification. The attack can be executed over any network connection the station is listening to and serves the web interface (AV:N), and there are no additional security measure sin place that need to be circumvented (AC:L), the attack does not rely on preconditions (AT:N). The attack does require authentication, but the level of authentication is irrelevant (PR:L), it does not require user interaction (UI:N). The attack has a small impact on the availability of the device (VC:N/VI:N/VA:L). There is no impact on subsequent systems. (SC:N/SI:N/SA:N). While this device is an EV charger handing significant amounts of power, we do not expect  this vulnerability to have a safety impact. 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 confidence

Multiple buffer overflow vulnerabilities exist in CGI binaries of Iocharger AC charger firmware versions before 24120701. These overflows can be exploited over the network with low privileges, potentially allowing remote code execution despite ASLR being enabled, though successful exploitation requires significant technical skill.

MitigationUpdate Iocharger AC charger firmware to version 24120701 or later to remediate the buffer overflow vulnerabilities.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Confirm the target device is an Iocharger AC charger by checking the device label, web interface, or administrative panel for the manufacturer and model information.
    Affected if The device is not an Iocharger AC charger (this CVE only affects Iocharger devices).
  2. Check the firmware version
    Access the charger administrative interface (typically via web browser or dedicated app) and locate the firmware version information in system settings, about page, or status section. Compare the version number to 24120701.
    Affected if The installed firmware version is any version before 24120701 (e.g., 24090101, 24050100, etc.).
  3. Verify CGI binary accessibility
    Check if the device web interface exposes CGI endpoints or binaries. This is typically found by accessing common paths like /cgi-bin/ or checking the web server configuration on the device.
    Affected if CGI binaries are enabled and accessible on the device web interface, as the buffer overflow vulnerabilities exist within these binaries.
  4. Assess network exposure
    Determine if the charger administrative interface is accessible from the network. Check firewall rules, port exposure (typically HTTP port 80 or HTTPS port 443), and whether the device is directly reachable on the network.
    Affected if The CGI interface is network-accessible, as the vulnerabilities can be exploited remotely over the network with low privileges.

A user is affected if they have an Iocharger AC charger with firmware version before 24120701 and the CGI web interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Iocharger AC charger firmware to version 24120701 or later to remediate the buffer overflow vulnerabilities.

Recommended fix Moderate confidence

Iocharger AC model charger firmware version 24120701 or later

  1. Obtain the Iocharger firmware version 24120701 or later from the official Iocharger vendor (iocharger.com) or authorized distribution channels
  2. Access the charging station's web interface using administrative credentials
  3. Navigate to the firmware update or system settings section
  4. Upload and apply the firmware update file following the vendor's documented upgrade procedure
  5. After the update completes, verify the firmware version has been updated to 24120701 or later
  6. Confirm the web interface and CGI binaries are functioning properly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43663 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43663 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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