How severe is GHSA-344m-qcjq-xgrf?

No CVSS score has been assigned to GHSA-344m-qcjq-xgrf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-344m-qcjq-xgrf?

GHSA-344m-qcjq-xgrf affects the following packages: sgx-dcap-quote-verify-python (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-344m-qcjq-xgrf?

Update sgx-dcap-quote-verify-python to 0.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-344m-qcjq-xgrf is resolved across your whole dependency graph.

How do I detect GHSA-344m-qcjq-xgrf in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sgx-dcap-quote-verify-python, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-344m-qcjq-xgrf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-344m-qcjq-xgrf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-344m-qcjq-xgrf can be triaged on real exposure rather than presence alone.

Is GHSA-344m-qcjq-xgrf actively exploited in the wild?

No public exploit code has been indexed for GHSA-344m-qcjq-xgrf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-344m-qcjq-xgrf published, and has it been updated?

GHSA-344m-qcjq-xgrf was published on February 14, 2023 and was last updated on November 30, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-344m-qcjq-xgrf — sgx-dcap-quote-verify-pyt…

GHSA-344m-qcjq-xgrf is a security vulnerability in sgx-dcap-quote-verify-python. A fix is available for sgx-dcap-quote-verify-python — see the affected versions and patch details below.

Vulnerable OpenSSL included in sgx-dcap-quote-verify-python

Published

Feb 14, 2023

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 30, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍sgx-dcap-quote-verify-python

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Analysis

The binding includes OpenSSL version 1.1.1s which is vulnerable to the vulnerabilities disclosed in OpenSSL Security Advisory from the 7th February 2023. The binding does not directly use OpenSSL. The binding calls the SGX Quote Verification Library which uses OpenSSL.

Explanation

The SGX Quote Verification Library uses OpenSSL as a dependency to perform its cryptographic operations and certificate verification.

The OpenSSL security advisory mentions multiple vulnerabilities but I believe the most concerning would be CVE-2023-0286 “X.400 address type confusion in X.509 GeneralName”. Its severity is rated high and the advisory states that “this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.”

Relying on CRLs obtained from an untrusted party is exactly what can happen when verifying a quote. For instance, the vulnerability could be triggered through the "sgx_qv_verify_quote" function which can take untrusted quote collateral as input. The quote collateral contains a CRL and certificate chains. The Quote Verification Library uses OpenSSL to verify the validity of those in order to establish the authenticity of the quote. Thus the vulnerability could be exploited with corrupted/forged collateral and quote.

Impact

According to the advisory the "vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service". Transitively I expect the same to be true for the Quote Verification Library. The denial of service impact is not much of a concern I believe since processing forged collateral would most likely stop the software from proceeding normally anyway (forged collateral should be rejected). The part regarding the ability to read memory contents, could result in information disclosure which is a real concern. The quote verification happens on the relying party end, which might use it to check enclave authenticity before providing sensitive data, this vulnerability could therefore result in the leakage of sensitive data.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`sgx-dcap-quote-verify-python`	all versions	0.0.3`pip install --upgrade 'sgx-dcap-quote-verify-python==0.0.3'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sgx-dcap-quote-verify-python, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sgx-dcap-quote-verify-python to 0.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-344m-qcjq-xgrf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-344m-qcjq-xgrf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-344m-qcjq-xgrf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

sgx-dcap-quote-verify-python includes a statically linked copy of OpenSSL. The version of OpenSSL included in sgx-dcap-quote-verify-python 0.0.1..0.0.2 is vulnerable to a security issue. More details about the OpenSSL vulnerabilities themselves can be found at https://www.openssl.org/news/secadv/20230207.txt. ## Analysis The binding includes OpenSSL version 1.1.1s which is vulnerable to the vulnerabilities disclosed in [OpenSSL Security Advisory from the 7th February 2023](https://www.openssl.org/news/secadv/20230207.txt). The binding does not directly use OpenSSL. The binding calls the SGX Q

O3 Security · Impact-Aware SCA

Is GHSA-344m-qcjq-xgrf in your dependencies?

O3 Security finds GHSA-344m-qcjq-xgrf across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works