CyberSecBulletin
CVE-2022-2347NVD status: Modified

Uboot: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2022-2347 is a high-severity out-of-bounds write vulnerability in Uboot, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with physical access to the device by an unauthenticated attacker, without any action from a user. Affected Uboot versions: 2022.07 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.58% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update RUGGEDCOM ROX MX5000 to V2.17.1 or a later version.
  2. Update RUGGEDCOM ROX MX5000RE to V2.17.1 or a later version.
  3. Update RUGGEDCOM ROX RX1400 to V2.17.1 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
UbootUboot2022.07 and earlierNot stated
SiemensRUGGEDCOM ROX MX5000before V2.17.1V2.17.1
SiemensRUGGEDCOM ROX MX5000REbefore V2.17.1V2.17.1
SiemensRUGGEDCOM ROX RX1400before V2.17.1V2.17.1
SiemensRUGGEDCOM ROX RX1500before V2.17.1V2.17.1
SiemensRUGGEDCOM ROX RX1501before V2.17.1V2.17.1
SiemensRUGGEDCOM ROX RX1510before V2.17.1V2.17.1
SiemensRUGGEDCOM ROX RX1511before V2.17.1V2.17.1
SiemensRUGGEDCOM ROX RX1512before V2.17.1V2.17.1
SiemensRUGGEDCOM ROX RX1524before V2.17.1V2.17.1
SiemensRUGGEDCOM ROX RX1536before V2.17.1V2.17.1
SiemensRUGGEDCOM ROX RX5000before V2.17.1V2.17.1
DenxU-boot2012.10 through 2022.07Not stated

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
PhysicalThe attacker must physically touch the device.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
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:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.7HighCNA (google.com)
CVSS 3.17.1HighNVD

Official description

There exists an unchecked length field in UBoot. The U-Boot DFU implementation does not bound the length field in USB DFU download setup packets, and it does not verify that the transfer direction corresponds to the specified command. Consequently, if a physical attacker crafts a USB DFU download setup packet with a `wLength` greater than 4096 bytes, they can write beyond the heap-allocated request buffer.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

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 Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

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

References

Technical write-ups (may include proof of concept)

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.