CVE-2024-26001 json
PHOENIX CONTACT: Out of bounds write only memory access
published 2y ago modified 4mo ago also EUVD-2024-23297
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- phoenixcontact charx_sec-3000_firmware 1.5.1
- phoenixcontact charx_sec-3050_firmware 1.5.1
- phoenixcontact charx_sec-3100_firmware 1.5.1
- phoenixcontact charx_sec-3150_firmware 1.5.1
Is CVE-2024-26001 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.87% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- PHOENIX CONTACT CHARX SEC-3000
- PHOENIX CONTACT CHARX SEC-3050
- PHOENIX CONTACT CHARX SEC-3100
- PHOENIX CONTACT CHARX SEC-3150
- phoenixcontact charx_sec_3000
- phoenixcontact charx_sec_3050
- phoenixcontact charx_sec_3100
- phoenixcontact charx_sec_3150
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
cert.vde.com
/en/advisories/VDE-2024-011
third-party-advisory
Sources
- CVE List CVE-2024-26001
- NVD CVE-2024-26001
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.