Cyber Resilience

CVE-2025-24003

Memory Safety in Phoenixcontact Charx Sec-3000 Firmware ≤ 1.6.5

Memory Safety
Published
08 July 2025
Modified
17 June 2026
CVSS Score v3.1 8.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
EPSS Score 0.0034 27th percentile
Risk Priority 61 floored blend · peak EPSS

Summary

CVE-2025-24003 is a high-severity Classic Buffer Overflow (CWE-120) vulnerability in Phoenixcontact Charx Sec-3000 Firmware. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-24003 is a buffer overflow vulnerability (CWE-120) affecting charging stations that comply with the German Calibration Law (Eichrecht). It enables unauthenticated remote attackers to trigger out-of-bounds writes via specially crafted MQTT messages, specifically targeting the EichrechtAgents component within these stations. The vulnerability has a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H), highlighting its high severity due to network accessibility, low attack complexity, and lack of required privileges.

An unauthenticated attacker with network access to the charging station can exploit this flaw by sending malicious MQTT messages, leading to a loss of integrity in the EichrechtAgents (I:L) and potential denial-of-service conditions for the affected stations (A:H). No user interaction is required, and exploitation does not impact confidentiality, making it feasible for remote adversaries to disrupt calibration compliance and station availability without authentication.

For mitigation details, security practitioners should consult the primary advisory from CERT VDE at https://certvde.com/en/advisories/VDE-2025-014, published on 2025-07-08.

EU & UK References

Vulnerability Data

An unauthenticated remote attacker can use MQTT messages to trigger out-of-bounds writes in charging stations complying with German Calibration Law, resulting in a loss of integrity for only EichrechtAgents and potential denial-of-service for these stations.

CWE(s)
CWE-120

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-24004Same product: Phoenixcontact Charx Sec-3000
CVE-2024-26003Same product: Phoenixcontact Charx Sec-3000
CVE-2024-26000Same product: Phoenixcontact Charx Sec-3000
CVE-2024-26004Same product: Phoenixcontact Charx Sec-3000
CVE-2024-26001Same product: Phoenixcontact Charx Sec-3000
CVE-2024-25997Same product: Phoenixcontact Charx Sec-3000
CVE-2024-25995Same product: Phoenixcontact Charx Sec-3000
CVE-2025-24002Same product: Phoenixcontact Charx Sec-3000
CVE-2025-24005Same product: Phoenixcontact Charx Sec-3000
CVE-2024-25999Same product: Phoenixcontact Charx Sec-3000

Affected Assets

phoenixcontact
charx sec-3000 firmware
≤ 1.6.5
phoenixcontact
charx sec-3050 firmware
≤ 1.6.5
phoenixcontact
charx sec-3100 firmware
≤ 1.6.5
phoenixcontact
charx sec-3150 firmware
≤ 1.6.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.2.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and analysis can find missing size checks before deployment.

SI-10 Information Input Validation good match

Input validation directly enforces size checks before buffer copies.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles require bounds checking and safe buffer handling in design.

SI-16 Memory Protection partial match

Memory protection limits the impact of an overflow once it occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure development practices directly enforce bounds checking and input validation that prevent classic buffer overflows.

ID.RA-01 partial match
prevents

Vulnerability identification processes such as code review or scanning detect classic buffer overflows before exploitation.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing unchecked buffer copies with corrected versions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
prevents

Secure coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect buffer overflows through fuzzing and static analysis, though it does not prevent them at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates processes that can include input validation and bounds checking to prevent buffer overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify input-size validation and safe buffer handling to mitigate classic buffer overflows.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles promote defensive coding patterns that reduce the likelihood of unchecked buffer copies.

References