CyberSecBulletin
CVE-2022-4046NVD status: Modified

CODESYS Control for BeagleBone SL: Improper Restriction of Operations within the Bounds of a Memory Buffer

CVE-2022-4046 is a high-severity improper restriction of operations within the bounds of a memory buffer vulnerability in CODESYS Control for BeagleBone SL from Codesys, with a CVSS 3.1 base score of 8.8 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. Affected CODESYS Control for BeagleBone SL versions: all. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.88% chance of exploitation within 30 days, higher than 60% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of CODESYS Control for BeagleBone SL you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
CODESYSCODESYS Control for BeagleBone SLallNot stated
CODESYSCODESYS Control for emPC-A/iMX6 SLallNot stated
CODESYSCODESYS Control for IOT2000 SLallNot stated
CODESYSCODESYS Control for Linux SLallNot stated
CODESYSCODESYS Control for PFC100 SLallNot stated
CODESYSCODESYS Control for PFC200 SLallNot stated
CODESYSCODESYS Control for PLCnext SLallNot stated
CODESYSCODESYS Control for Raspberry Pi SLallNot stated
CODESYSCODESYS Control for WAGO Touch Panels 600 SLallNot stated
CODESYSCODESYS Control RTE (for Beckhoff CX) SLallNot stated
CODESYSCODESYS Control RTE (SL)allNot stated
CODESYSCODESYS Control Runtime System ToolkitallNot stated
CODESYSCODESYS Control Win (SL)allNot stated
CODESYSCODESYS HMI (SL)allNot stated
CodesysControl For Beaglebone SlNot specified in the recordNot stated
CodesysControl For Empc-a/imx6 SlNot specified in the recordNot stated
CodesysControl For Iot2000 SlNot specified in the recordNot stated
CodesysControl For Linux SlNot specified in the recordNot stated
CodesysControl For Pfc100 SlNot specified in the recordNot stated
CodesysControl For Pfc200 SlNot specified in the recordNot stated
CodesysControl For Plcnext SlNot specified in the recordNot stated
CodesysControl For Raspberry Pi SlNot specified in the recordNot stated
CodesysControl For Wago Touch Panels 600 SlNot specified in the recordNot stated
CodesysControl Rte SlNot specified in the recordNot stated
CodesysControl Rte Sl (for Beckhoff Cx)Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 3 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
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:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cert.vde.com).

Official description

In CODESYS Control in multiple versions a improper restriction of operations within the bounds of a memory buffer allow an remote attacker with user privileges to gain full access of the device.

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.

More Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities (CWE-119)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Other vulnerabilities in CODESYS Control for BeagleBone SL

All CODESYS Control for BeagleBone SL vulnerabilities

Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities

Spotted an error? Tell us.