Integrity loss and restart via unsafe buffer copy
Published Jul 8, 2025 · Updated Jul 8, 2025
Classic buffer overflow in Phoenix Contact CHARX SEC-3xxx firmware 1.6.5 and earlier allows physically proximate attackers to disrupt charging stations. The Eichrecht agent uses sprintf to place attacker-controlled display data into a fixed 0x800-byte stack buffer without enforcing its size. Physical USB-C display access is required; exploitation causes integrity loss and a temporary service interruption until the watchdog restarts the station.
Summary
What happened
Classic buffer overflow in Phoenix Contact CHARX SEC-3xxx firmware 1.6.5 and earlier allows physically proximate attackers to disrupt charging stations. The Eichrecht agent uses sprintf to place attacker-controlled display data into a fixed 0x800-byte stack buffer without enforcing its size. Physical USB-C display access is required; exploitation causes integrity loss and a temporary service interruption until the watchdog restarts the station.
The record
- CVE
- CVE-2025-24004
- Published
- Jul 8, 2025
- Updated
- Jul 8, 2025
- Vendor
- Phoenix Contact
- Product
- CHARX SEC-3100
- Classifications
- CWE-120, T0814
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Jul 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.0 <=1.6.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- charx-sec-exploits proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- CHARX SEC-3150 proof-of-concept exploit chainexploit chain
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo