Rust advisories / libpulse-binding
Vulnerability HighRUSTSEC-2018-0021 · libpulse-binding
RUSTSEC-2018-0021: Use-after-free with objects returned by `Stream`'s `get_format_info` and `get_context` methods
Short answerA security vulnerability in the libpulse-binding crate: Use-after-free with objects returned by `Stream`'s `get_format_info` and `get_context` methods. GitHub rates it High. Fixed in 1.2.1: update to a fixed version.
| Crate | libpulse-binding |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 1.2.1. |
| Fixed in | 1.2.1 |
| Severity | High (GitHub rating) |
| Published | 2018-06-15 |
| Last changed | 2026-10-12 |
| Also known as | CVE-2018-25027, CVE-2018-25028, GHSA-ghpq-vjxw-ch5w, GHSA-hxjf-h2mh-r6hj, GHSA-jqpv-jm4m-86j9 |
| Affected functions | libpulse_binding::stream::Stream::get_context, libpulse_binding::stream::Stream::get_format_info |
What to do
- See which version you have:
cargo tree -i libpulse-binding(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p libpulse-binding. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplelibpulse-binding = "1.2.1") 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
Affected versions contained a pair of use-after-free issues with the objects returned by the get_format_info and get_context methods of Stream objects. These objects were mistakenly being constructed without setting an important flag to prevent destruction of the underlying C objects they reference upon their own destruction.
References
- Package: crates.io/crates/libpulse-binding
- Advisory: rustsec.org/advisories/RUSTSEC-2018-0021.html
- Web: github.com/jnqnfe/pulse-binding-rust/commit/e6930e16573f0b6d12d6628ba5de59147d6f9e95
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 libpulse-binding
Up next
Same cratelibpulse-binding: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?