CODESYS Control RTE (SL): Incorrect Permission Assignment for Critical Resource
CVE-2022-22516 is a high-severity incorrect permission assignment for critical resource vulnerability in CODESYS Control RTE (SL) from Codesys, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system 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 0.26% chance of exploitation within 30 days, which is low compared with other 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 Development System V3 | V3.5.18.0 up to, but not including, V3.5.18.0 | V3.5.18.0 |
| Codesys | Control Rte Sl | before 3.5.18.0 | 3.5.18.0 |
| Codesys | Control Rte Sl (for Beckhoff Cx) | before 3.5.18.0 | 3.5.18.0 |
| Codesys | Control Win Sl | before 3.5.18.0 | 3.5.18.0 |
| Codesys | Development System | before 3.5.18.0 | 3.5.18.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- 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
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA (cert.vde.com) |
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 2.0 | 7.2 | High | NVD |
Official description
The SysDrv3S driver in the CODESYS Control runtime system on Microsoft Windows allows any system user to read and write within restricted memory space.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
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 Incorrect Permission Assignment for Critical Resource vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 7.6 High severity
- 7.8 High severity
- 9.1 Critical severity
- 7.3 High severity
Spotted an error? Tell us.