Is libpulse-binding affected by CVE-2018-25027?

crates.io libpulse-binding is affected in <1.2.1.

Is CVE-2018-25027 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 1.3%.

high

CVE-2018-25027

Q: Is CVE-2018-25027 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 1.3%.

crates.io · libpulse-binding

Summary

Use After Free in libpulse-binding

Severity: high
EPSS: 1.3% (p67)
Also known as: CVE-2018-25028, GHSA-ghpq-vjxw-ch5w, GHSA-hxjf-h2mh-r6hj, GHSA-jqpv-jm4m-86j9, RUSTSEC-2018-0021
Published: 2022-01-06

References

https://github.com/jnqnfe/pulse-binding-rust/security/advisories/GHSA-ghpq-vjxw-ch5w
https://nvd.nist.gov/vuln/detail/CVE-2018-25027
https://github.com/jnqnfe/pulse-binding-rust

Related advisories

CVE-2019-25055 — high · crates.io/libpulse-binding
CVE-2018-25001 — medium · crates.io/libpulse-binding

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.