# CVE-2024-32883: MCUboot Injection attack of unprotected TLV values

> Attackers can inject unprotected TLV entries into MCUboot images, potentially bypassing security checks or altering attestation records.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GO-2024-2799

## What is CVE-2024-32883?

CVE-2024-32883 is a high-severity vulnerability in mcu-tools mcuboot, published on 26 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MCUboot is a secure bootloader for 32-bits microcontrollers. MCUboot uses a TLV (tag-length-value) structure to represent the meta data associated with an image.  The TLVs themselves are divided into two sections, a protected and an unprotected section. The protected TLV entries are included as part of the image signature to avoid tampering. However, the code does not distinguish which TLV entries should be protected or not, so it is possible for an attacker to add unprotected TLV entries that should be protected. Currently, the primary protected TLV entries should be the dependency indication, and the boot record. An injected dependency value would primarily result in an otherwise acceptable image being rejected. A boot record injection could allow fields in a later attestation record to include data not intended, which could cause an image to appear to have properties that it should not have. As a workaround, disable the boot record functionality.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

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

1 open source package ship an affected version, including github.com/mcu-tools/mcuboot.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/mcu-tools/mcuboot` | Go | All versions | None |

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

No fix has been published for CVE-2024-32883 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-32883 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32883 is a high-severity vulnerability in mcu-tools mcuboot, published on 26 Apr 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-32883 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/mcu-tools/mcuboot (Go): affected all versions; no fix listed

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-32883/ (Markdown: https://insights.sbomify.com/CVE-2024-32883/index.md)
```

## Sources

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

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