# CVE-2025-24004: USB-C Buffer Overflow via Display Interface in EV Charging Stations

> A physical attacker can trigger a buffer overflow via USB-C, causing integrity loss and temporary denial of service in EV charging stations.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-v2p4-fgcv-96mw

## What is CVE-2025-24004?

CVE-2025-24004 is a medium-severity memory corruption vulnerability in Phoenix Contact CHARX SEC-3000, published on 8 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A physical attacker with access to the device display via USB-C can send a message to the device which triggers an unsecure copy to a buffer resulting in loss of integrity and a temporary denial-of-service for the stations until they got restarted by the watchdog.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-24004?

It affects 4 products.


Products: Phoenixcontact Charx Sec-3000 Firmware, Phoenixcontact Charx Sec-3050 Firmware, Phoenixcontact Charx Sec-3100 Firmware, Phoenixcontact Charx Sec-3150 Firmware.

## How do I fix CVE-2025-24004?

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

## Is CVE-2025-24004 being exploited?

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

## Other vulnerabilities in Phoenix Contact CHARX SEC-3000

- [CVE-2025-25270](https://insights.sbomify.com/CVE-2025-25270/): Remote Code Execution via Unauthenticated Configuration Manipulation (critical 9.8)
- [CVE-2024-25995](https://insights.sbomify.com/CVE-2024-25995/): PHOENIX CONTACT: Remote code execution in CHARX Series (critical 9.8)
- [CVE-2025-25268](https://insights.sbomify.com/CVE-2025-25268/): Unauthenticated Configuration Access via Exposed API Endpoint (high 8.8)
- [CVE-2025-25271](https://insights.sbomify.com/CVE-2025-25271/): OCPP Backend Configuration via Insecure Defaults (high 8.8)
- [CVE-2024-26288](https://insights.sbomify.com/CVE-2024-26288/): PHOENIX CONTACT: Lack of SSL support in CHARX Series (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24004 and fix it if it is affected.

What it is: CVE-2025-24004 is a medium-severity memory corruption vulnerability in Phoenix Contact CHARX SEC-3000, published on 8 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24004 in the wild and no public exploit code.

Affected product: Phoenix Contact CHARX SEC-3000. 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-2025-24004/ (Markdown: https://insights.sbomify.com/CVE-2025-24004/index.md)
```

## Sources

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

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