dcap-qvl
Python bindings for DCAP (Data Center Attestation Primitives) quote verification library
View on Github
Activity
- Latest release
- 2w ago
- Total releases
- 23
- Cadence
- ~11 days
- Last 12 months
- 16
Reach
- Stars
- 44
Details
- License
- MIT
- First release
- Feb 11, 2025
| Version | Released | |
|---|---|---|
0.6.3
patch
| ||
0.6.1
patch
| ||
0.6.0
minor
| ||
0.5.3
patch
| ||
0.5.2
minor
| ||
0.4.0
minor
| ||
0.3.13
patch
| ||
0.3.12
patch
| ||
0.3.11
patch
| ||
0.3.10
patch
| ||
0.3.9
patch
| ||
0.3.8
patch
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.3.7
patch
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.3.6
patch
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.3.5
patch
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.3.4
patch
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.3.2
patch
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.3.0
minor
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.2.2
minor
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.1.0
initial
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.1.3
patch
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.1.2
patch
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev | ||
0.1.1
patch
1 CVE
CVE-2026-22696
PYSEC-2026-326
GHSA-796p-j2gh-9m2q
Jun 29, 2026
dcap-qvl has Missing Verification for QE Identity
Critical
Network
Low
None
None
ImpactThis 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. ConsequencesAn 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 impactedAll deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. PatchesThe 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 WorkaroundsThere are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. CreditThis bug was reported by Rahul Saxena saxenism@bluethroatlabs.com. 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
Fixed in
0.3.9
References Updated Jul 01, 2026 · Source: OSV.dev |