RUSTSEC-2018-0020: Possible use-after-free with `proplist::Iterator`

What to do

1. See which version you have: cargo tree -i libpulse-binding (it also shows which of your dependencies pulls it in).
2. 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 example libpulse-binding = "2.5.0") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

Affected versions contained a possible use-after-free issue with property list iteration due to a lack of a lifetime constraint tying the lifetime of a proplist::Iterator to the Proplist object for which it was created. This made it possible for users, without experiencing a compiler error/warning, to destroy the Proplist object before the iterator, thus destroying the underlying C object the iterator works upon, before the iterator may be finished with it.

This impacts all versions of the crate before 2.5.0 back to 1.0.5. Before version 1.0.5 the function that produces the iterator was broken to the point of being useless.

References

• Package: crates.io/crates/libpulse-binding
• Advisory: rustsec.org/advisories/RUSTSEC-2018-0020.html
• Web: github.com/jnqnfe/pulse-binding-rust/commit/9e31c82d71749619387cb9d0c9698134d05b28c9

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

• VulnerabilityRUSTSEC-2018-0021 · 2018-06-15Use-after-free with objects returned by `Stream`'s `get_format_info` and `get_context` methods
• UnsoundRUSTSEC-2019-0038 · 2019-03-10Fix for UB in failure to catch panics crossing FFI boundaries

Full security history of libpulse-binding