Rust advisories / libpulse-binding
Unsound MediumRUSTSEC-2019-0038 · libpulse-binding
RUSTSEC-2019-0038: Fix for UB in failure to catch panics crossing FFI boundaries
Short answerlibpulse-binding has an API that can cause undefined behaviour from safe code: Fix for UB in failure to catch panics crossing FFI boundaries. Fixed in 2.6.0.
| Crate | libpulse-binding |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Before 2.6.0. |
| Fixed in | 2.6.0 |
| Severity | Medium (GitHub rating) |
| Published | 2019-03-10 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2019-25055, GHSA-wcxc-jf6c-8rx9, GHSA-xvcg-2q82-r87j |
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 = "2.6.0") 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 of this crate failed to catch panics crossing FFI boundaries via callbacks, which is a form of UB. This flaw was corrected by this commit which was included in version 2.6.0.
References
- Package: crates.io/crates/libpulse-binding
- Advisory: rustsec.org/advisories/RUSTSEC-2019-0038.html
- Web: github.com/jnqnfe/pulse-binding-rust/commit/7fd282aef7787577c385aed88cb25d004b85f494
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?