In multiple CODESYS products in multiple versions an unauthorized, remote attacker may use a…
CVE-2022-47391 is a high-severity improper input validation 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.19.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.86% chance of exploitation within 30 days, higher than 80% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update CODESYS Control RTE (SL) to V3.5.19.0 or a later version.
- Update CODESYS Control RTE (for Beckhoff CX) SL to V3.5.19.0 or a later version.
- Update CODESYS Control Win (SL) to V3.5.19.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) | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS Control RTE (for Beckhoff CX) SL | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS Control Win (SL) | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS Control Runtime System Toolkit | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS Safety SIL2 Runtime Toolkit | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS Safety SIL2 PSP | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS Edge Gateway for Windows | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS Gateway | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS HMI (SL) | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS Development System V3 | V0.0.0.0 up to, but not including, V3.5.19.0 | V3.5.19.0 |
| CODESYS | CODESYS Control for BeagleBone SL | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| CODESYS | CODESYS Control for emPC-A/iMX6 SL | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| CODESYS | CODESYS Control for IOT2000 SL | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| CODESYS | CODESYS Control for Linux SL | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| CODESYS | CODESYS Control for PFC100 SL | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| CODESYS | CODESYS Control for PFC200 SL | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| CODESYS | CODESYS Control for PLCnext SL | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| CODESYS | CODESYS Control for Raspberry Pi SL | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| CODESYS | CODESYS Control for WAGO Touch Panels 600 SL | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| CODESYS | CODESYS Edge Gateway for Linux | V0.0.0.0 up to, but not including, V4.8.0.0 | V4.8.0.0 |
| Codesys | Control For Beaglebone Sl | before 4.8.0.0 | 4.8.0.0 |
| Codesys | Control For Empc-a/imx6 Sl | before 4.8.0.0 | 4.8.0.0 |
| Codesys | Control For Iot2000 Sl | before 4.8.0.0 | 4.8.0.0 |
| Codesys | Control For Linux Sl | before 4.8.0.0 | 4.8.0.0 |
| Codesys | Control For Pfc100 Sl | before 4.8.0.0 | 4.8.0.0 |
Version data comes from the organisation that assigned the CVE; 12 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 CNA (cert.vde.com).
Official description
In multiple CODESYS products in multiple versions an unauthorized, remote attacker may use a improper input validation vulnerability to read from invalid addresses leading to a denial of service.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- 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 Improper Input Validation vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 7.5 High severity
- 7.2 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.