CVE-2024-57258

Code execution via allocator integer overflows

Published Feb 18, 2025 · Updated May 12, 2026

U-Boot before 2025.01-rc1 and RUGGEDCOM ROX before 2.17.1 contain allocator overflows that allow physically proximate attackers to execute code. The sbrk and request2size allocation paths fail to reject arithmetic overflow, while x86_64 pointer-difference handling can miscalculate allocation sizes for crafted SquashFS data. Exploitation requires control of filesystem structures presented during boot and can bypass a verified-boot chain of trust through memory corruption.

CVSS severity7.1
High
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

U-Boot before 2025.01-rc1 and RUGGEDCOM ROX before 2.17.1 contain allocator overflows that allow physically proximate attackers to execute code. The sbrk and request2size allocation paths fail to reject arithmetic overflow, while x86_64 pointer-difference handling can miscalculate allocation sizes for crafted SquashFS data. Exploitation requires control of filesystem structures presented during boot and can bypass a verified-boot chain of trust through memory corruption.

The record

CVE
CVE-2024-57258
Published
Feb 18, 2025
Updated
May 12, 2026
Vendor
Siemens
Product
RUGGEDCOM ROX RX1500
Classifications
CWE-190, T1037
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 18, 2025CVE publishedPublication date reported by the CVE source.
  2. May 12, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <V2.17.1

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Siemens · RUGGEDCOM ROX RX1500version=0 <V2.17.1
Siemens · RUGGEDCOM ROX RX5000version=0 <V2.17.1
Siemens · RUGGEDCOM ROX RX1511version=0 <V2.17.1
Siemens · RUGGEDCOM ROX MX5000REversion=0 <V2.17.1
Siemens · RUGGEDCOM ROX RX1536version=0 <V2.17.1
DENX Software Engineering GmbH · U-Bootversion=0 <2025.01-rc1
Siemens · RUGGEDCOM ROX RX1512version=0 <V2.17.1
Siemens · RUGGEDCOM ROX RX1510version=0 <V2.17.1
Siemens · RUGGEDCOM ROX RX1524version=0 <V2.17.1
Siemens · RUGGEDCOM ROX RX1501version=0 <V2.17.1
Siemens · RUGGEDCOM ROX RX1400version=0 <V2.17.1
Siemens · RUGGEDCOM ROX MX5000version=0 <V2.17.1

Published CVSS scores

7.1MITRECVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-190Integer Overflow or Wraparound
T1037Boot or Logon Autostart Execution: Boot or Logon Initialization Scripts

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo