How severe is GHSA-q445-7m23-qrmw?

GHSA-q445-7m23-qrmw has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-q445-7m23-qrmw?

GHSA-q445-7m23-qrmw affects the following packages: openssl (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-q445-7m23-qrmw?

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.

How do I detect GHSA-q445-7m23-qrmw in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q445-7m23-qrmw 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-q445-7m23-qrmw?

O3 pinpoints whether GHSA-q445-7m23-qrmw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q445-7m23-qrmw actively exploited in the wild?

No public exploit code has been indexed for GHSA-q445-7m23-qrmw 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-q445-7m23-qrmw published, and has it been updated?

GHSA-q445-7m23-qrmw was published on July 22, 2024 and was last updated on February 4, 2026. 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

GHSA-q445-7m23-qrmw

MEDIUM

openssl's `MemBio::get_buf` has undefined behavior with empty buffers

Also known asRUSTSEC-2024-0357

Published

Jul 22, 2024

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

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

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`openssl`	all versions	0.10.66

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether GHSA-q445-7m23-qrmw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q445-7m23-qrmw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-q445-7m23-qrmw in your dependencies?

O3 detects GHSA-q445-7m23-qrmw across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works