Panic on a GCP launch endorsement without TDX measurements
Historical advisory saved 11 Nov 2026 09:25:56 UTC. The publisher may have updated it since then. Latest advisory.
osv · RUSTSEC-2026-0480
Published`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](https://github.com/IntelLabs/tdx-workload-attestation/pull/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](https://borystsyrulnikov.dev).
- Source published
- 10 Nov 2026 12:00:00 UTC
- Source modified
- 11 Nov 2026 08:45:02 UTC
- Saved here
- 11 Nov 2026 09:25:56 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V4 · CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N