dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-51997

HIGH · 8.1 CVSS v3.1 Published 2024-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A man-in-the-middle attacker can intercept the ART (Attestation Results Token) and replace the 'jwk' (JSON Web Key) in the token payload with their own public key. The attacker then signs the modified token with their corresponding private key. The verifier (CoCo Verification Demander like KBS) still validates the signature successfully because it trusts any key present in the token, failing to detect the key substitution. This allows attackers to forge valid attestation tokens and potentially gain access to confidential guests and secrets.

MitigationUpgrade to Trustee version 0.8.2 or later. There are no workarounds; the upgrade is mandatory to address the cryptographic verification bypass.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Trustee installation
    Search for the Trustee binary or service: which trustee, systemctl list-units | grep trustee, or check common installation paths like /usr/bin/trustee, /usr/local/bin/trustee, or C:\Program Files\Trustee\trustee.exe on Windows
    Affected if Trustee is not found - the product may not be installed, so this CVE does not apply
  2. Determine the installed Trustee version
    Run 'trustee --version' or 'trustee -v' to obtain the version number; if it's a Windows service, right-click the executable, select Properties, and view the File Version field
    Affected if The version is lower than 0.8.2 (e.g., 0.8.1, 0.8.0, or earlier) - these versions contain the vulnerable jwk validation logic
  3. Verify ART verification is configured
    Inspect Trustee's configuration files (commonly in /etc/trustee/, /opt/trustee/config/, or a config.yaml file) for settings related to Attestation Results Token verification, such as 'attestation', 'art', 'kbs', or 'coco' configuration sections
    Affected if ART verification is enabled in configuration - the vulnerability only affects environments using CoCo attestation token validation with the jwk field processing
  4. Check if the verifier connects to a KBS (Key Broker Service)
    Review Trustee logs or configuration for references to a Key Broker Service endpoint or 'verifier' connections; look for URLs containing 'kbs' or 'attestation' in the config
    Affected if Trustee is configured to validate attestation tokens from a KBS - this is the attack surface where a man-in-the-middle could inject a forged token with a substituted key

The environment is affected if Trustee version is present and is lower than 0.8.2, and ART/KBS attestation verification is enabled in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Trustee version 0.8.2 or later. There are no workarounds; the upgrade is mandatory to address the cryptographic verification bypass.

Recommended fix High confidence

0.8.2

  1. Identify the current version of Trustee being used (check v0.8.0 or earlier versions are affected)
  2. Obtain the fixed version 0.8.2 from the official Trustee repository at github.com
  3. Follow the project's standard upgrade procedure to update to version 0.8.2
  4. Verify the installation of version 0.8.2 is successful
  5. Test the attestation functionality to confirm the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51997 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51997 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data