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-42067, GHSA-w4mf-755j-wjwc
verify_x509_cert does not check the certificate validity period
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, 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.
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