dcap-qvl has Missing Verification for QE Identity
The advisory, in context
Impact
This vulnerability 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.
Consequences
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.
Who is impacted
All deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected.
Patches
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.
Workarounds
There are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified.
Credit
This bug was reported by Rahul Saxena saxenism@bluethroatlabs.com.
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
Earlier releases before 0.3.9
Fixed in 0.3.9
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.3.9"
}
],
"type": "SEMVER"
}
],
"versions": []
}Earlier releases before 0.3.9
Fixed in 0.3.9
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.3.9"
}
],
"type": "SEMVER"
}
],
"versions": []
}Earlier releases through 0.3.3 (inclusive)
No fix recorded for this interval.
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.3.3"
}
],
"type": "SEMVER"
}
],
"versions": []
}Earlier releases through 0.3.3 (inclusive)
No fix recorded for this interval.
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.3.3"
}
],
"type": "SEMVER"
}
],
"versions": []
}Earlier releases before 0.3.9
Fixed in 0.3.9
12 explicitly affected versions
0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.2.2, 0.3.0, 0.3.2, 0.3.4, 0.3.5, 0.3.6, 0.3.7, 0.3.8
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.3.9"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.0",
"0.1.1",
"0.1.2",
"0.1.3",
"0.2.2",
"0.3.0",
"0.3.2",
"0.3.4",
"0.3.5",
"0.3.6",
"0.3.7",
"0.3.8"
]
}