How severe is GHSA-9qwg-crg9-m2vc?

No CVSS score has been assigned to GHSA-9qwg-crg9-m2vc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9qwg-crg9-m2vc?

GHSA-9qwg-crg9-m2vc affects the following packages: openssl (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-9qwg-crg9-m2vc?

Update openssl to 0.10.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9qwg-crg9-m2vc is resolved across your whole dependency graph.

How do I detect GHSA-9qwg-crg9-m2vc in my crates.io dependencies?

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

How do I mitigate GHSA-9qwg-crg9-m2vc 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-9qwg-crg9-m2vc?

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

Is GHSA-9qwg-crg9-m2vc actively exploited in the wild?

No public exploit code has been indexed for GHSA-9qwg-crg9-m2vc 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-9qwg-crg9-m2vc published, and has it been updated?

GHSA-9qwg-crg9-m2vc was published on March 24, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-9qwg-crg9-m2vc — openssl

Fix: sfackler/rust-openssl#1854

GHSA-9qwg-crg9-m2vc is a security vulnerability in openssl. A fix is available for openssl — see the affected versions and patch details below.

`openssl` `SubjectAlternativeName` and `ExtendedKeyUsage::other` allow arbitrary file read

Also known asRUSTSEC-2023-0023

Published

Mar 24, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀openssl

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

Description

SubjectAlternativeName and ExtendedKeyUsage arguments were parsed using the OpenSSL function X509V3_EXT_nconf. This function parses all input using an OpenSSL mini-language which can perform arbitrary file reads.

Thanks to David Benjamin (Google) for reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`openssl`	≥ 0.9.7&&< 0.10.48	0.10.48`cargo update -p openssl --precise 0.10.48`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openssl to 0.10.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9qwg-crg9-m2vc 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-9qwg-crg9-m2vc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-9qwg-crg9-m2vc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`SubjectAlternativeName` and `ExtendedKeyUsage` arguments were parsed using the OpenSSL function `X509V3_EXT_nconf`. This function parses all input using an OpenSSL mini-language which can perform arbitrary file reads. Thanks to David Benjamin (Google) for reporting this issue.

O3 Security · Impact-Aware SCA

Is GHSA-9qwg-crg9-m2vc in your dependencies?

O3 Security finds GHSA-9qwg-crg9-m2vc across crates.io 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