CODESYS Control RTE (SL): Use of Insufficiently Random Values
CVE-2022-22517 is a high-severity use of insufficiently random values vulnerability in CODESYS Control RTE (SL) from Codesys, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version V3.5.18.0 as the first without the flaw, so updating CODESYS Control RTE (SL) to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.52% chance of exploitation within 30 days, higher than 75% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update CODESYS Control RTE (SL) to V3.5.18.0 or a later version.
- Update CODESYS Control RTE (for Beckhoff CX) SL to V3.5.18.0 or a later version.
- Update CODESYS Control Win (SL) to V3.5.18.0 or a later version.
- Read the advisory on customers.codesys.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| CODESYS | CODESYS Control RTE (SL) | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS Control RTE (for Beckhoff CX) SL | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS Control Win (SL) | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS Gateway | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS Edge Gateway for Windows | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS HMI (SL) | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS Development System V3 | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS Control Runtime System Toolkit | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS Embedded Target Visu Toolkit | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS Remote Target Visu Toolkit | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS Control for BeagleBone SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Control for Beckhoff CX9020 SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Control for emPC-A/iMX6 SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Control for IOT2000 SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Control for Linux SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Control for PFC100 SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Control for PFC200 SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Control for PLCnext SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Control for Raspberry Pi SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Control for WAGO Touch Panels 600 SL | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS Edge Gateway for Linux | V4.5.0.0 up to, but not including, V4.5.0.0 | V4.5.0.0 |
| CODESYS | CODESYS OPC DA Server SL | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| CODESYS | CODESYS PLCHandler | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| Codesys | Control For Beaglebone Sl | before 4.5.0.0 | 4.5.0.0 |
| Codesys | Control For Beckhoff Cx9020 | before 4.5.0.0 | 4.5.0.0 |
Version data comes from the organisation that assigned the CVE; 18 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (cert.vde.com) |
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | NVD |
Official description
An unauthenticated, remote attacker can disrupt existing communication channels between CODESYS products by guessing a valid channel ID and injecting packets. This results in the communication channel to be closed.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Insufficiently Random Values
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
How developers prevent this class of flaw
- Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds. In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts. Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a random enough number.
- Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
- Use products or modules that conform to FIPS 140-2 to avoid obvious entropy problems. Consult FIPS 140-2 Annex C (Approved Random Number Generators).
More Use of Insufficiently Random Values vulnerabilities (CWE-330)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in CODESYS Control RTE (SL)
- 7.5 High severity
- 8.1 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
Recent Use of Insufficiently Random Values vulnerabilities
- 9.1 Critical severity
- 9.8 Critical severity
- 9.1 Critical severity
Spotted an error? Tell us.