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

CVE-2024-43661

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
The <redacted>.so library, which is used by <redacted>, is vulnerable to a buffer overflow in the code that handles the deletion of certificates. This buffer overflow can be triggered by providing a long file path to the <redacted> action of the <redacted>.exe CGI binary or to the <redacted>.sh CGI script. This binary or script will write this file path to <redacted>, which is then read by <redacted>.so This issue affects Iocharger firmware for AC models before version 24120701. Likelihood: Moderate – An attacker will have to find this exploit by either obtaining the binaries involved in this vulnerability, or by trial and error. Furthermore, the attacker will need a (low privilege) account to gain access to the <redacted>.exe CGI binary or <redacted>.sh script to trigger the vulnerability, or convince a user with such access send an HTTP request that triggers it. Impact: High – The <redacted> process, which we assume is responsible for OCPP communication, will keep crashing after performing the exploit. This happens because the buffer overflow causes the process to segfault before <redacted> is removed. This means that, even though <redacted> is automatically restarted, it will crash again as soon as it tries to parse the text file. 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 leads to reducred availability of the device (VC:N/VI:N/VA:H). THere is not impact on subsequent systems. (SC:N/SI:N/SA:N). Alltough this device is an EV charger handing significant amounts of power, we do not forsee a safety impact. The attack can be automated (AU:Y). Because the DoS condition is written to disk persistantly, it cannot be recovered by the user (R:I).

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

Buffer overflow vulnerability in iocharger.so library when handling certificate deletion. Attackers provide an overly long file path via CGI binaries/scripts, which gets written to disk and then read by the library, causing a buffer overflow that triggers a segfault in the OCPP communication process.

MitigationUpdate Iocharger AC firmware to version 24120701 or later to address the vulnerability.

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
    Access the charger web interface or check the device label/metadata to confirm it is an Iocharger AC EV charger model. Note the firmware version displayed in the system info or status page.
    Affected if Device is an Iocharger AC EV charger with firmware version lower than 24120701
  2. Check the installed firmware version
    Log into the charger's web interface and navigate to the firmware or system information page. Record the exact firmware version string displayed.
    Affected if Firmware version is any version prior to 24120701 (e.g., 24110101, 24090102, etc.)
  3. Verify the vulnerable shared library exists
    If you have shell access or can extract firmware, locate the shared library (.so) handling certificate operations. Check its file version or build timestamp if exposed.
    Affected if The certificate handling .so library is present and predates the patch date corresponding to version 24120701
  4. Confirm web interface and CGI scripts are accessible
    Attempt to access the charger web interface over HTTP/HTTPS. Identify if CGI binaries or scripts related to certificate management are reachable (e.g., endpoints for certificate upload or deletion).
    Affected if The web interface and CGI endpoints for certificate management are exposed on the network
  5. Check if OCPP communication is configured
    In the charger web interface, navigate to the OCPP or network configuration section. Verify if OCPP is enabled and a connection to a central system is configured.
    Affected if OCPP is enabled and the charger attempts to communicate with a central system, as this is the component that segfaults when the buffer overflow is triggered

The environment is affected if the device is an Iocharger AC EV charger running firmware version lower than 24120701 with its web interface and OCPP functionality exposed on the network.

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 firmware to version 24120701 or later to address the vulnerability.

Recommended fix High confidence

Iocharger AC firmware version 24120701 or later

  1. Obtain the Iocharger firmware version 24120701 or later from the official Iocharger vendor source (iocharger.com or authorized distribution channels)
  2. Access the Iocharger device administrative interface using valid credentials
  3. Navigate to the firmware update section of the web management interface
  4. Upload and apply the firmware update following the vendor's documented upgrade procedure
  5. Verify the firmware was successfully applied by checking the device version information
  6. Confirm the device is functioning normally after the upgrade
Caveat Review vendor release notes for any configuration or operational changes required by the new firmware version

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43661 — 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-43661 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