`openssl` `SubjectAlternativeName` and `ExtendedKeyUsage::other` allow arbitrary file readGHSA-9qwg-crg9-m2vc
Fix: sfackler/rust-openssl#1854GHSA-9qwg-crg9-m2vc is a security vulnerability in openssl. A fix is available for openssl — see the affected versions and patch details below.
Real-World Exposure
opensslReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | openssl | ≥ 0.9.7&&< 0.10.48 | 0.10.48cargo update -p openssl --precise 0.10.48 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
Frequently Asked Questions
Is GHSA-9qwg-crg9-m2vc in your dependencies?
Find it across crates.io, including transitive dependencies.