openssl's `MemBio::get_buf` has undefined behavior with empty buffersGHSA-q445-7m23-qrmw
MEDIUMFix: sfackler/rust-openssl#2266GHSA-q445-7m23-qrmw is a medium-severity (CVSS 6.5) 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
Previously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | openssl | all versions | 0.10.66cargo update -p openssl --precise 0.10.66 |
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.66 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q445-7m23-qrmw 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-q445-7m23-qrmw in your dependencies?
Find it across crates.io, including transitive dependencies.