# CVE-2024-51997: The Attestation Results Token can be arbitrarily modified without being detected in Trustee

> Attackers can modify Attestation Results Tokens to bypass verification, allowing unauthorized access to secrets in Trustee deployments.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Nov 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-7jc6-j236-vvjw

## What is CVE-2024-51997?

CVE-2024-51997 is a high-severity authentication bypass vulnerability in confidential-containers trustee, published on 8 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Trustee is a set of tools and components for attesting confidential guests and providing secrets to them. The ART (**Attestation Results Token**) token, generated by AS, could be manipulated by MITM attacker, but the verifier (CoCo Verification Demander like KBS) could still verify it successfully. In the payload of ART token, the ‘jwk’ could be replaced by attacker with his own pub key. Then attacker can use his own corresponding private key to sign the crafted ART token. Based on current code implementation (v0.8.0), such replacement and modification can not be detected. This issue has been addressed in version 0.8.2 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2024-51997 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51997 is a high-severity authentication bypass vulnerability in confidential-containers trustee, published on 8 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51997 in the wild and no public exploit code.

Affected product: confidential-containers trustee. 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-51997/ (Markdown: https://insights.sbomify.com/CVE-2024-51997/index.md)
```

## Sources

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

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