Critical severity · published Mar 12, 2024
CVE-2024-26001
An unauthenticated remote attacker can write memory out of bounds due to improper input validation in the MQTT stack
9.8
CVSS
0.9%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.9% · higher than 59% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CS
Charx Sec-3000 Firmware · Phoenixcontact
before 1.5.1 · source: NVD
CS
Charx Sec-3050 Firmware · Phoenixcontact
before 1.5.1 · source: NVD
CS
Charx Sec-3100 Firmware · Phoenixcontact
before 1.5.1 · source: NVD
CS
Charx Sec-3150 Firmware · Phoenixcontact
before 1.5.1 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-26001
CVE.org
https://www.cve.org/CVERecord?id=CVE-2024-26001
Third Party Advisory
https://cert.vde.com/en/advisories/VDE-2024-011
More from Charx Sec-3000 Firmware
9.8
CVE-2025-25270
An unauthenticated remote attacker can alter the device configuration in a way to get remote code execution as root with specific configurations
9.8
CVE-2024-6788
A remote unauthenticated attacker can use the firmware update feature on the LAN interface of the device to reset the password for the predefined, low-privileged user “user-app”…
9.8
CVE-2024-25996
An unauthenticated remote attacker can perform a remote code execution due to an origin validation error
9.8
CVE-2024-25995
An unauthenticated remote attacker can modify configurations to perform a remote code execution, gain root rights or perform an DoS due to improper input validation
8.8
CVE-2025-25271
An unauthenticated adjacent attacker is able to configure a new OCPP backend, due to insecure defaults for the configuration interface