dcap-qvl has Missing Verification for QE Identity
Phala-Network dcap-qvl
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| dcap-qvl crates.io |
|
|
| @phala/dcap-qvl npm |
|
|
| @phala/dcap-qvl-web npm |
Phala-Network dcap-qvl
| Product | Affected | Fixed in |
|---|---|---|
| dcap-qvl crates.io |
|
|
| @phala/dcap-qvl npm |
|
|
| @phala/dcap-qvl-web npm |
≤ 0.3.3| No fix yet |
| @phala/dcap-qvl-node npm |
| No fix yet |
| dcap-qvl PyPI |
|
|
dcap-qvl implements the quote verification logic for DCAP (Data Center Attestation Primitives). A vulnerability present in versions prior to 0.3.9 involves a critical gap in the cryptographic verification process within the dcap-qvl. The library fetches QE Identity collateral (including qe_identity, qe_identity_signature, and qe_identity_issuer_chain) from the PCCS. However, it skips to verify the QE Identity signature against its certificate chain and does not enforce policy constraints on the QE Report. An attacker can forge the QE Identity data to whitelist a malicious or non-Intel Quoting Enclave. This allows the attacker to forge the QE and sign untrusted quotes that the verifier will accept as valid. Effectively, this bypasses the entire remote attestation security model, as the verifier can no longer trust the entity responsible for signing the quotes. All deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. The vulnerability has been patched in dcap-qvl version 0.3.9. The fix implements the missing cryptographic verification for the QE Identity signature and enforces the required checks for MRSIGNER, ISVPRODID, and ISVSVN against the QE Report. Users of the `@phala/dcap-qvl-node` and `@phala/dcap-qvl-web` packages should switch to the pure JavaScript implementation, `@phala/dcap-qvl`. There are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified.
From the CVE record · GitHub_M
dcap-qvl does not verify the QE Identity signature against its certificate chain or enforce required QE Report checks. When a verifier processes forged QE Identity data, an attacker can make it accept untrusted quotes signed by a malicious or non-Intel Quoting Enclave.
Check SGX or TDX quote verification deployments using crates.io dcap-qvl, npm @phala/dcap-qvl, or PyPI dcap-qvl below 0.3.9, or npm @phala/dcap-qvl-web or @phala/dcap-qvl-node through 0.3.3.