# GHSA-q445-7m23-qrmw: openssl's `MemBio::get_buf` has undefined behavior with empty buffers

> Undefined behavior in MemBio::get_buf with empty buffers can cause assertion failures or crashes in debug builds.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2024
- **Also known as:** RUSTSEC-2024-0357

## What is GHSA-q445-7m23-qrmw?

GHSA-q445-7m23-qrmw is a memory corruption vulnerability in openssl, published on 21 Jul 2024. 

### Official 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.

## Which versions are affected by GHSA-q445-7m23-qrmw?

3 open source packages ship an affected version, including openssl.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl` | crates.io | All versions | 0.10.66 |
| `openssl` | crates.io | All versions | 0.10.66 |
| `openssl` | crates.io | From 0.0.0-0 | 0.10.66 |

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

Upgrade openssl to 0.10.66 or later.

## Is GHSA-q445-7m23-qrmw being exploited?

There is no known exploitation of GHSA-q445-7m23-qrmw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-q445-7m23-qrmw and fix it if it is affected.

What it is: GHSA-q445-7m23-qrmw is a memory corruption vulnerability in openssl, published on 21 Jul 2024. 
Exploitation: There is no known exploitation of GHSA-q445-7m23-qrmw in the wild and no public exploit code.

Affected packages and fixed versions:
- openssl (crates.io): affected all versions; fixed in 0.10.66
- openssl (crates.io): affected all versions; fixed in 0.10.66
- openssl (crates.io): affected from 0.0.0-0; fixed in 0.10.66

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-q445-7m23-qrmw/ (Markdown: https://insights.sbomify.com/GHSA-q445-7m23-qrmw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-q445-7m23-qrmw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-q445-7m23-qrmw/
Summaries are generated and may contain mistakes; the official description above is the record.