tdx_workload_attestation
Affected
- introduced
0.0.0-0, fixed0.2.0(semver)
Fixed versions
0.2.0
Fix
- Fixed version
0.2.0cargo update -p tdx_workload_attestation --precise 0.2.0
Advisory
Also known as: CVE-2026-40693, GHSA-gwf2-8595-qw97
Panic on a GCP launch endorsement without TDX measurements
GcpTdxHost::verify_launch_endorsement(), available with the host-gcp-tdx
feature, read uefi_golden.tdx.measurements[0] without checking that the
golden measurement contains a TDX measurement. If a launch endorsement's
golden measurement had no TDX measurements, the call panicked with an index
out of bounds instead of returning an error.
The panic is reached only after the endorsement's signing certificate and
signature have been verified. Triggering it therefore requires a correctly
signed endorsement that lacks TDX measurements.
Intel describes the issue as improper input validation and classifies it as
denial of service, with a CVSS 4.0 base score of 5.7, in INTEL-SA-01520.
The flaw was corrected in
#87, released
in 0.2.0. The function now returns Error::ParseError when the TDX
measurement structure is missing or empty.
Reported by Borys Tsyrulnikov.
Not rated by the source.
0.0.0-0, fixed 0.2.0 (semver)0.2.0
0.2.0cargo update -p tdx_workload_attestation --precise 0.2.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0