CyberSecBulletin
CVE-2024-57258NVD status: Modified

U-Boot: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2024-57258 is a high-severity integer overflow or wraparound vulnerability in U-Boot from Denx, 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 2025.01-rc1 as the first without the flaw, so updating U-Boot to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.25% 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 U-Boot to 2025.01-rc1 or a later version.
  2. Update RUGGEDCOM ROX MX5000 to V2.17.1 or a later version.
  3. Update RUGGEDCOM ROX MX5000RE to V2.17.1 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
DenxU-Bootbefore 2025.01-rc12025.01-rc1
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

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 systemScoreSeverityScored by
CVSS 3.17.1HighCNA (mitre.org)
CVSS 3.17.8HighNVD

Official description

Integer overflows in memory allocation in Das U-Boot before 2025.01-rc1 occur for a crafted squashfs filesystem via sbrk, via request2size, or because ptrdiff_t is mishandled on x86_64.

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

The underlying weakness: Integer Overflow or Wraparound

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How developers prevent this class of flaw

  • Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).

More Integer Overflow or Wraparound vulnerabilities (CWE-190)

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

Other vulnerabilities in U-Boot

All U-Boot vulnerabilities

Recent Integer Overflow or Wraparound vulnerabilities

Spotted an error? Tell us.