CVE-2018-25001: Libpulse binding Use After Free Vulnerability

MODERATE
Advisory Identifier: GHSA-f56g-chqp-22m9
CVSS 6.5
CWE-416
Published
Advisory Summary

CVE-2018-25001 is a MODERATE (CVSS 6.5) use after free vulnerability (CWE-416: Use After Free) affecting Libpulse binding libraries in the crates.io ecosystem. The issue involves use after free in libpulse-binding. Remediation is available by upgrading affected packages to version 2.5.0.

CVE-2018-25001 at a Glance

CVE Identifier CVE-2018-25001
GHSA Identifier GHSA-f56g-chqp-22m9
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-416: Use After Free
Affected Product Libpulse binding
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2018-25001

To remediate this vulnerability, upgrade all affected Libpulse binding dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

libpulse-binding fixed: 2.5.0
Upgrade libpulse-binding to 2.5.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for libpulse-binding

How to Check if You Are Affected

To determine whether your application is affected by CVE-2018-25001, inspect your project dependencies for Libpulse binding:

inspect dependencies for libpulse-binding

Analyze the terminal output to locate any version of Libpulse binding in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.5.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-416: Use After Free, where 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. In Libpulse binding, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

CVE-2018-25001 Affected Libpulse binding Versions

1 component(s)
Fixed Versions:
2.5.0
Product / Package Ecosystem Affected Versions Fixed Version
libpulse-binding
crates.io
≥ 1.0.5
< 2.5.0
2.5.0

References

Frequently Asked Questions

What is CVE-2018-25001?
CVE-2018-25001 is a security vulnerability in Libpulse binding involving Use after free in libpulse-binding under CWE-416: Use After Free.
Which Libpulse binding versions are affected?
Affected versions include releases prior to 2.5.0 across affected packages: libpulse-binding.
What version fixes CVE-2018-25001?
Upgrading to 2.5.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is libpulse-binding affected?
Yes, libpulse-binding is affected in releases prior to 2.5.0. Upgrade your dependency to 2.5.0 or later.
What is the CVSS score of CVE-2018-25001?
CVE-2018-25001 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2018-25001?
CVE-2018-25001 is classified under CWE-416: 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.).
How can I check crates.io dependencies for CVE-2018-25001?
Run the dependency tree command: 'inspect dependencies for libpulse-binding'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f56g-chqp-22m9",
  "modified" : "2026-01-22T22:36:03Z",
  "published" : "2024-02-03T00:28:45Z",
  "aliases" : [ "CVE-2018-25001" ],
  "summary" : "Use after free in libpulse-binding",
  "details" : "### Overview\n\nVersion 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.\n\nThis advisory is being written retrospectively, having previously only been noted in the changelog. No CVE assignment was sought.\n\nThis 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.\n\n### Patches\n\nUsers are required to update to version 2.5.0 or newer.\n\nVersions older than 2.5.0 have been yanked from crates.io as of the 22nd of October 2020.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "libpulse-binding"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.5"
      }, {
        "fixed" : "2.5.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/jnqnfe/pulse-binding-rust/security/advisories/GHSA-f56g-chqp-22m9"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2018-25001"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jnqnfe/pulse-binding-rust/commit/9e31c82d71749619387cb9d0c9698134d05b28c9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jnqnfe/pulse-binding-rust"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2018-0020.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-416" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-02-03T00:28:45Z",
    "nvd_published_at" : null
  }
}