CODESYS Control RTE (SL): Improper Restriction of Operations within the Bounds of a Memory Buffer
CVE-2022-22514 is a high-severity improper restriction of operations within the bounds of a memory buffer vulnerability in CODESYS Control RTE (SL) from Codesys, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, 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.04% chance of exploitation within 30 days, higher than 64% 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.
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 | 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 |
| Codesys | Control For Empc-a/imx6 Sl | before 4.5.0.0 | 4.5.0.0 |
| Codesys | Control For Iot2000 Sl | before 4.5.0.0 | 4.5.0.0 |
Version data comes from the organisation that assigned the CVE; 16 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
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.1 | High | CNA (cert.vde.com) |
| CVSS 3.1 | 7.1 | High | NVD |
| CVSS 2.0 | 4.9 | Medium | NVD |
Official description
An authenticated, remote attacker can gain access to a dereferenced pointer contained in a request. The accesses can subsequently lead to local overwriting of memory in the CmpTraceMgr, whereby the attacker can neither gain the values read internally nor control the values to be written. If invalid memory is accessed, this results in a crash.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
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 Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.