`openssl` `X509StoreRef::objects` is unsoundGHSA-xphf-cx8h-7q9g
Fix: sfackler/rust-openssl@cf9681aGHSA-xphf-cx8h-7q9g 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
This function returned a reference into an OpenSSL datastructure, but there was no way to ensure OpenSSL would not mutate the datastructure behind one's back.
Use of this function should be replaced with X509StoreRef::all_certificates.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | openssl | ≥ 0.10.29&&< 0.10.60 | 0.10.60cargo update -p openssl --precise 0.10.60 |
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.60 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xphf-cx8h-7q9g 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-xphf-cx8h-7q9g in your dependencies?
Find it across crates.io, including transitive dependencies.