CVE-2018-25001: An issue was discovered in the libpulse-binding crate before 2.5.0 for Rust

This month

MEDIUM 6.5UPGRADE

CVE-2018-25001 is a medium-severity flaw (CVSS 6.5) affecting libpulse-binding. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in the libpulse-binding crate before 2.5.0 for Rust. proplist::Iterator can cause a use-after-free.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.0% (top 37%)
CISA exploited list	No
Weakness	CWE-416
Published	2020-12-31
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: libpulse-binding project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-12-31 10:15 UTCPublished CVE record published
2026-06-17 01:54 UTCUpdated Record last modified

libpulse-binding project libpulse-binding UPGRADE

Affected: >= 1.0.5 and < 2.5.0

Fixed in: 2.5.0

Safe to downgrade to: a release before 1.0.5

1. Check installed version

apt-cache policy libpulse-binding || rpm -q libpulse-binding || libpulse-binding --version

2. UPGRADE to 2.5.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libpulse-binding

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libpulse-binding

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.5 (Debian / Ubuntu)

apt-cache madison libpulse-binding sudo apt install libpulse-binding=<VERSION_BEFORE_1.0.5> sudo apt-mark hold libpulse-binding

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list libpulse-binding sudo dnf downgrade libpulse-binding-<VERSION_BEFORE_1.0.5> sudo dnf versionlock add libpulse-binding

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-25001?

libpulse-binding: upgrade to 2.5.0. Exact commands for each OS are on this page.

Is CVE-2018-25001 being exploited?

CVE-2018-25001 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-25001 affect?

CVE-2018-25001 affects libpulse-binding. Severity is medium (CVSS 6.5). An issue was discovered in the libpulse-binding crate before 2.5.0 for Rust. proplist::Iterator can cause a use-after-free.

How urgent is CVE-2018-25001?

Priority 43/100. Public exploit reference

Related CVEs

CVE-2019-25055 HIGH 7.5 UPGRADE An issue was discovered in the libpulse-binding crate before 2.6.0 for Rust
CVE-2018-25028 HIGH 7.5 UPGRADE An issue was discovered in the libpulse-binding crate before 1.2.1 for Rust
CVE-2018-25027 HIGH 7.5 UPGRADE An issue was discovered in the libpulse-binding crate before 1.2.1 for Rust

References

← Back to latest CVEs