# CVE-2024-6564: Buffer overflow in Rensas RCAR

> A buffer overflow in Renesas RCAR firmware allows attackers to bypass secure boot and potentially execute arbitrary code.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-6564, GHSA-4f2h-f89q-3w95, UBUNTU-CVE-2024-6564

## What is CVE-2024-6564?

CVE-2024-6564 is a medium-severity memory corruption vulnerability in Renesas rcar_gen3_v2.5, published on 8 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in "rcar_dev_init"  due to using due to using untrusted data (rcar_image_number) as a loop counter before verifying it against RCAR_MAX_BL3X_IMAGE. This could lead to a full bypass of secure boot.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-6564?

It affects 1 product.


Products: Renesas Arm-Trusted-Firmware.

## How do I fix CVE-2024-6564?

Apply the vendor's patch.

## Is CVE-2024-6564 being exploited?

There is no known exploitation of CVE-2024-6564 in the wild and no public exploit code.

## Other vulnerabilities in Renesas rcar_gen3_v2.5

- [CVE-2024-6563](https://insights.sbomify.com/CVE-2024-6563/): Buffer Overflow Arbitrary Write (high 7.5)
- [CVE-2024-1633](https://insights.sbomify.com/CVE-2024-1633/): FIP Header Integer Overflow (low 2.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6564 and fix it if it is affected.

What it is: CVE-2024-6564 is a medium-severity memory corruption vulnerability in Renesas rcar_gen3_v2.5, published on 8 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6564 in the wild and no public exploit code.

Affected product: Renesas rcar_gen3_v2.5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6564/ (Markdown: https://insights.sbomify.com/CVE-2024-6564/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6564
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6564
- OSV: https://osv.dev/vulnerability/CVE-2024-6564

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6564/
Summaries are generated and may contain mistakes; the official description above is the record.