# CVE-2024-43663: Buffer overflow vulnerabilities in CGI scripts lead to segfault

> Buffer overflows in CGI scripts allow authenticated attackers to cause denial of service or potentially achieve remote code execution on Iocharger AC charging stations.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/AU:Y/R:A`)
- **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-g42r-fh8w-cm5m

## What is CVE-2024-43663?

CVE-2024-43663 is a medium-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

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).

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-43663?


## How do I fix CVE-2024-43663?

No fix has been published for CVE-2024-43663 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-43663 being exploited?

There is no known exploitation of CVE-2024-43663 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-43663 and fix it if it is affected.

What it is: CVE-2024-43663 is a medium-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-43663 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-43663/ (Markdown: https://insights.sbomify.com/CVE-2024-43663/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-43663
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-43663
- OSV: https://osv.dev/vulnerability/CVE-2024-43663

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-43663/
Summaries are generated and may contain mistakes; the official description above is the record.