RustSec logo

History ⋅ Edit ⋅ JSON (OSV)

RUSTSEC-2026-0481

verify_x509_cert does not check the certificate validity period

Reported
Issued
Package
tdx_workload_attestation (crates.io)
Type
Vulnerability
Categories
Keywords
#tdx #attestation #x509 #certificate
Aliases
References
CVSS Score
5.9 MEDIUM
CVSS Details
Attack Complexity
Low
Attack Requirements
Present
Attack Vector
Local
Privileges Required
None
Availability Impact to the Subsequent System
None
Confidentiality Impact to the Subsequent System
None
Integrity Impact to the Subsequent System
None
User Interaction
None
Availability Impact to the Vulnerable System
None
Confidentiality Impact to the Vulnerable System
None
Integrity Impact to the Vulnerable System
High
CVSS Vector
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
Patched
  • >=0.2.0
Affected Functions
Version
tdx_workload_attestation::verification::x509::verify_x509_cert
  • <0.2.0

Description

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.

Advisory available under CC0-1.0 license.