
Cloud Vulnerability DB
A community-led vulnerabilities database
The libpulse-binding Rust crate versions 1.0.5 through 2.5.0 contained a potential use-after-free vulnerability in the proplist::Iterator implementation. The issue was discovered and fixed in version 2.5.0, released on December 22, 2018. The vulnerability stemmed from a lack of lifetime constraint between the proplist::Iterator and the Proplist object, which could allow the Proplist object to be destroyed before the iterator completed its operations (GitHub Advisory, RustSec).
The vulnerability arose from a design flaw where there was no lifetime association linking the Iterator object to the Proplist object. This made it possible for users to destroy the Proplist object before the iterator, leaving the Iterator working on a freed C object. The issue could be triggered without any compiler errors or warnings. The vulnerability is tracked as CVE-2018-25001 with a CVSS v3.1 score of 6.5 (Moderate), indicating Network attack vector, Low attack complexity, Low privileges required, and No user interaction needed (RustSec).
If exploited, this vulnerability could lead to use-after-free conditions when working with property list iterations. While the actual impact in practice was likely limited due to the specific usage patterns required to trigger the vulnerability, it represented a significant memory safety issue that could potentially lead to memory corruption (GitHub Advisory).
The vulnerability was fixed in version 2.5.0 of libpulse-binding by implementing proper lifetime constraints between the Iterator and Proplist objects. Users are required to update to version 2.5.0 or newer. All versions older than 2.5.0 have been yanked from crates.io as of October 22, 2020 (GitHub Advisory).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."