FIP Header Integer Overflow

Description

During the secure boot, bl2 (the second stage of the bootloader) loops over images defined in the table “bl2_mem_params_descs”. For each image, the bl2 reads the image length and destination from the image’s certificate. Because of the way of reading from the image, which base on 32-bit unsigned integer value, it can result to an integer overflow. An attacker can bypass memory range restriction and write data out of buffer bounds, which could result in bypass of secure boot. Affected git version from c2f286820471ed276c57e603762bd831873e5a17 until (not

Scores

EPSS (exploitation in 30 days)

0.14% · top 96% of all CVEs (7 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 2.0.

Weakness

• CWE-190 Integer Overflow or Wraparound (opens in a new tab)All about CWE-190 and its CVEs

Affected products

• Renesas · rcar_gen3_v2.5

  • affected v2.5

References (1)

• https://asrg.io/security-advisories/CVE-2024-1633/ (opens in a new tab)x_transferred

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2024-1633](https://trackcve.app/badge/CVE-2024-1633.svg)](https://trackcve.app/cve/CVE-2024-1633)

Record last updated 1 Aug 2024, 18:48 UTC.