Vulnerability MediumRUSTSEC-2024-0357 · openssl
RUSTSEC-2024-0357: `MemBio::get_buf` has undefined behavior with empty buffers
Short answerA security vulnerability in the openssl crate: `MemBio::get_buf` has undefined behavior with empty buffers. GitHub rates it Medium. Fixed in 0.10.66: update to a fixed version.
| Crate | openssl |
|---|---|
| Type | Vulnerability |
| Affected versions | Before 0.10.66. |
| Fixed in | 0.10.66 |
| Severity | Medium (GitHub rating) |
| Published | 2024-07-21 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-q445-7m23-qrmw |
| Affected functions | openssl::bio::MemBio::get_buf |
What to do
- See which version you have:
cargo tree -i openssl(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p openssl. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleopenssl = "0.10.66") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
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.
References
- Package: crates.io/crates/openssl
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0357.html
- Web: github.com/sfackler/rust-openssl/pull/2266
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for openssl
- Vulnerability HighRUSTSEC-2016-0001 · 2016-11-05SSL/TLS MitM vulnerability due to insecure defaults
- Vulnerability CriticalRUSTSEC-2018-0010 · 2018-06-01Use after free in CMS Signing
- VulnerabilityRUSTSEC-2023-0022 · 2023-03-24`openssl` `X509NameBuilder::build` returned object is not thread safe
- VulnerabilityRUSTSEC-2023-0023 · 2023-03-24`openssl` `SubjectAlternativeName` and `ExtendedKeyUsage::other` allow arbitrary file read
- VulnerabilityRUSTSEC-2023-0024 · 2023-03-24`openssl` `X509Extension::new` and `X509Extension::new_nid` null pointer dereference
- VulnerabilityRUSTSEC-2023-0044 · 2023-06-20`openssl` `X509VerifyParamRef::set_host` buffer over-read
- UnsoundRUSTSEC-2023-0072 · 2023-11-23`openssl` `X509StoreRef::objects` is unsound
- VulnerabilityRUSTSEC-2025-0004 · 2025-02-02ssl::select_next_proto use after free
Up next
Same crateopenssl: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?