Skip to content
Fencer Intel
medium —

GHSA-4fcv-w3qc-ppgg json

rust-openssl Use-After-Free in `Md::fetch` and `Cipher::fetch`

published last yr. modified 2mo ago also RUSTSEC-2025-0022

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io openssl 0.10.72

Is GHSA-4fcv-w3qc-ppgg in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io openssl
>=0.10.39, <0.10.72
0.10.72

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.