CVE-2024-1633: FIP Header Integer Overflow
First published: Mon Feb 19 2024(Updated: )
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
Credit: cve@asrg.io
| Affected Software | Affected Version | How to fix |
|---|---|---|
| ARM Trusted Firmware-A | >=c2f286820471ed276c57e603762bd831873e5a17< | |
| All of | ||
| Arm Trusted Firmware | =rcar_gen3_2.5 | |
| Any of | ||
| Renesas R-car D3e | ||
| Renesas R-car E3e | ||
| Renesas R-Car H3e | ||
| Renesas R-car H3ne | ||
| Renesas R-car M3e | ||
| Renesas R-car M3ne | ||
| Renesas R-car V3h | ||
| Renesas R-Car V3H2 | ||
| Renesas R-car V3m |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-1633?
CVE-2024-1633 is classified as a high severity vulnerability due to its potential to compromise the secure boot process.
How do I fix CVE-2024-1633?
To mitigate CVE-2024-1633, users should upgrade to the latest version of Arm Trusted Firmware or apply available patches specific to their environment.
What software is affected by CVE-2024-1633?
CVE-2024-1633 affects various versions of Arm Trusted Firmware and Renesas arm-trusted-firmware on specific hardware platforms.
What is the impact of CVE-2024-1633 on system security?
CVE-2024-1633 can lead to unauthorized access or execution of malicious code during the boot process, undermining the system's integrity.
Is there a known exploit for CVE-2024-1633?
As of now, there are no public exploits reported that take advantage of CVE-2024-1633, but the vulnerability poses significant risk to affected systems.
- agent/weakness
- agent/references
- agent/description
- agent/title
- agent/type
- agent/first-publish-date
- agent/severity
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/last-modified-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/tags
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- vendor/arm
- canonical/arm trusted firmware-a
- vendor/renesas
- canonical/arm trusted firmware
- version/arm trusted firmware/rcar_gen3_2.5
- canonical/renesas r-car d3e
- canonical/renesas r-car e3e
- canonical/renesas r-car h3e
- canonical/renesas r-car h3ne
- canonical/renesas r-car m3e
- canonical/renesas r-car m3ne
- canonical/renesas r-car v3h
- canonical/renesas r-car v3h2
- canonical/renesas r-car v3m