`verify_x509_cert` does not check the certificate validity period
Historical advisory saved 11 Nov 2026 09:25:56 UTC. The publisher may have updated it since then. Latest advisory.
osv · RUSTSEC-2026-0481
Published`tdx_workload_attestation::verification::x509::verify_x509_cert()`, available with the `host-verification` feature, checked that `issuer_cert` issued `cert` and verified the certificate signature. It did not check the certificate's validity period, so it accepted expired and not-yet-valid certificates. With the `host-gcp-tdx` feature, this function validates the GCP launch endorsement signing certificate against the GCE confidential-computing TCB root certificate. A signing certificate outside its validity period was therefore still accepted during launch endorsement verification. Intel describes the issue as improper certificate validation and classifies it as escalation of privilege, with a CVSS 4.0 base score of 5.9, in INTEL-SA-01520. The flaw was corrected in [#86](https://github.com/IntelLabs/tdx-workload-attestation/pull/86), released in 0.2.0. The function now returns `Ok(false)` when the current time is outside the certificate's `notBefore`/`notAfter` range. 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:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N