# GHSA-4fcv-w3qc-ppgg: rust-openssl Use-After-Free in `Md::fetch` and `Cipher::fetch`

> A use-after-free vulnerability in rust-openssl allows attackers to potentially execute arbitrary code or cause denial of service when specific properties are passed.

- **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:** 4 Apr 2025
- **Also known as:** RUSTSEC-2025-0022

## What is GHSA-4fcv-w3qc-ppgg?

GHSA-4fcv-w3qc-ppgg is an use after free vulnerability in openssl, published on 4 Apr 2025. 

### Official description

When a `Some(...)` value was passed to the `properties` argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to `CString::drop`'s behavior).

The maintainers thank [quitbug](https://github.com/quitbug/) for reporting this vulnerability to us.

## Which versions are affected by GHSA-4fcv-w3qc-ppgg?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl` | crates.io | From 0.10.39 | 0.10.72 |
| `openssl` | crates.io | From 0.10.39 | 0.10.72 |
| `openssl` | crates.io | From 0.10.39 | 0.10.72 |

## How do I fix GHSA-4fcv-w3qc-ppgg?

Upgrade openssl to 0.10.72 or later.

## Is GHSA-4fcv-w3qc-ppgg being exploited?

There is no known exploitation of GHSA-4fcv-w3qc-ppgg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4fcv-w3qc-ppgg and fix it if it is affected.

What it is: GHSA-4fcv-w3qc-ppgg is an use after free vulnerability in openssl, published on 4 Apr 2025. 
Exploitation: There is no known exploitation of GHSA-4fcv-w3qc-ppgg in the wild and no public exploit code.

Affected packages and fixed versions:
- openssl (crates.io): affected from 0.10.39; fixed in 0.10.72
- openssl (crates.io): affected from 0.10.39; fixed in 0.10.72
- openssl (crates.io): affected from 0.10.39; fixed in 0.10.72

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-4fcv-w3qc-ppgg/ (Markdown: https://insights.sbomify.com/GHSA-4fcv-w3qc-ppgg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4fcv-w3qc-ppgg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4fcv-w3qc-ppgg/
Summaries are generated and may contain mistakes; the official description above is the record.