# CVE-2024-43662: Authenticated arbitrary file upload to /tmp/ and /tmp/upload/

> Authenticated attackers can upload arbitrary files to temporary directories on Iocharger EV chargers, potentially modifying device integrity.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/AU:Y`)
- **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-2q25-7xw9-h7cj

## What is CVE-2024-43662?

CVE-2024-43662 is a medium-severity 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 <redacted>.exe or <redacted>.exe CGI binary can be used to upload arbitrary files to /tmp/upload/ or /tmp/ respectively as any user, although the user interface for uploading files is only shown to the iocadmin user.

This issue affects Iocharger firmware for AC models before version 24120701.

Likelihood: Moderate – An attacker will need to have knowledge of this CGI binary, e.g. by finding it in firmware. Furthermore, the attacker will need a (low privilege) account to gain access to the <redacted>.exe or <redacted>.exe CGI binary and upload the file, or convince a user with such access to upload it.

Impact: Low – The attacker can upload arbitrary files to /tmp/upload/ or /tmp/. However, the attacker is unable to access or use these files without other vulnerabilities.

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). Artitrary files can be uploaded, be these files will not be in a location where they can influence confidentiality or availability and have a minimal impact on device integrity (VC:N/VI:L/VA:N).  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-862 (Missing Authorization), CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2024-43662 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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