Unauthenticated code execution via unchecked JSON array length
Published Mar 12, 2024 · Updated Jan 24, 2025
Out-of-bounds write in Phoenix Contact CHARX SEC-3xxx firmware 1.5.0 and earlier allows remote attackers to execute code through MQTT. The MQTT handler copies user-supplied JSON-array data into a buffer without validating its length, producing an out-of-bounds memory write. No authentication is required, but address randomization makes the required brute-force attempts unreliable; successful execution runs as the charx-ea user.
Summary
What happened
Out-of-bounds write in Phoenix Contact CHARX SEC-3xxx firmware 1.5.0 and earlier allows remote attackers to execute code through MQTT. The MQTT handler copies user-supplied JSON-array data into a buffer without validating its length, producing an out-of-bounds memory write. No authentication is required, but address randomization makes the required brute-force attempts unreliable; successful execution runs as the charx-ea user.
The record
- CVE
- CVE-2024-26001
- Published
- Mar 12, 2024
- Updated
- Jan 24, 2025
- Vendor
- Phoenix Contact
- Product
- CHARX SEC-3100
- Classifications
- CWE-787, T0866
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2024CVE publishedPublication date reported by the CVE source.
- Jan 24, 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 <=1.5.0
What conditions does exploitation require?
What is affected?
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.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
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