Skip to content

Use after free in libpulse-binding

Moderate severity GitHub Reviewed Published Oct 22, 2020 in jnqnfe/pulse-binding-rust • Updated Jan 22, 2026

Package

cargo libpulse-binding (Rust)

Affected versions

>= 1.0.5, < 2.5.0

Patched versions

2.5.0

Description

Overview

Version 2.5.0 of the libpulse-binding Rust crate, released on the 22nd of December 2018, fixed a potential 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 advisory is being written retrospectively, having previously only been noted in the changelog. No CVE assignment was sought.

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.

Patches

Users are required to update to version 2.5.0 or newer.

Versions older than 2.5.0 have been yanked from crates.io as of the 22nd of October 2020.

References

@jnqnfe jnqnfe published to jnqnfe/pulse-binding-rust Oct 22, 2020
Published to the GitHub Advisory Database Feb 3, 2024
Reviewed Feb 3, 2024
Last updated Jan 22, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(44th percentile)

Weaknesses

Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer. Learn more on MITRE.

CVE ID

CVE-2018-25001

GHSA ID

GHSA-f56g-chqp-22m9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.