CVE-2024-26001 PHOENIX CONTACT: Out of bounds write only memory access
Unauthenticated remote attackers can cause out-of-bounds memory writes in the MQTT stack, potentially leading to code execution or denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-26001?
CVE-2024-26001 is a high-severity memory corruption vulnerability in PHOENIX CONTACT CHARX SEC-3000, published on 12 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An unauthenticated remote attacker can write memory out of bounds due to improper input validation in the MQTT stack. The brute force attack is not always successful because of memory randomization.
Weakness: CWE-787
Which versions are affected by CVE-2024-26001?
It affects 4 products.
Products include 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-2024-26001?
No fix has been published for CVE-2024-26001 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2024-26001 being exploited?
There is no known exploitation of CVE-2024-26001 in the wild and no public exploit code.
Other vulnerabilities in PHOENIX CONTACT CHARX SEC-3000
- CVE-2025-25270 Remote Code Execution via Unauthenticated Configuration Manipulation
- CVE-2024-25995 PHOENIX CONTACT: Remote code execution in CHARX Series
- CVE-2025-25268 Unauthenticated Configuration Access via Exposed API Endpoint
- CVE-2025-25271 OCPP Backend Configuration via Insecure Defaults
- CVE-2024-26288 PHOENIX CONTACT: Lack of SSL support in CHARX Series
Sources
Also known as GHSA-3p73-75xq-v9wv.