# CVE-2024-43661: Buffer overflow in .so leads to DoS of OCPP service > A buffer overflow in the OCPP service library allows authenticated attackers to cause a persistent denial of service by triggering a crash loop. - **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/AU:Y/R:I`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 9 Jan 2025 - **Updated:** 11 Mar 2025 - **Also known as:** GHSA-6wxc-jqg3-v947 ## What is CVE-2024-43661? CVE-2024-43661 is a high-severity memory corruption vulnerability in Iocharger firmware for AC models, published on 9 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description The .so library, which is used by , 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 action of the .exe CGI binary or to the .sh CGI script. This binary or script will write this file path to , which is then read by .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 .exe CGI binary or .sh script to trigger the vulnerability, or convince a user with such access send an HTTP request that triggers it. Impact: High – The 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 is removed. This means that, even though 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). Weakness: CWE-121 (Stack-based Buffer Overflow) ## Which versions are affected by CVE-2024-43661? ## How do I fix CVE-2024-43661? No fix has been published for CVE-2024-43661 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-43661 being exploited? There is no known exploitation of CVE-2024-43661 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-43661 and fix it if it is affected. What it is: CVE-2024-43661 is a high-severity memory corruption vulnerability in Iocharger firmware for AC models, published on 9 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-43661 in the wild and no public exploit code. Affected product: Iocharger firmware for AC models. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-43661/ (Markdown: https://insights.sbomify.com/CVE-2024-43661/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-43661 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-43661 - OSV: https://osv.dev/vulnerability/CVE-2024-43661 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-43661/ Summaries are generated and may contain mistakes; the official description above is the record.