CVE-2018-25027 json
Use After Free in libpulse-binding
published 2018-06-15 8 y ago modified 2026-10-12 27 d ago also CVE-2018-25028 , GHSA-ghpq-vjxw-ch5w , GHSA-hxjf-h2mh-r6hj , GHSA-jqpv-jm4m-86j9 , RUSTSEC-2018-0021 , EUVD-2022-0623
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
An issue was discovered in the libpulse-binding crate before 1.2.1 for Rust. get_format_info can cause a use-after-free.
Patch / fix
- crates.io libpulse-binding 1.2.1
- libpulse-binding_project libpulse-binding 1.2.1
Exploit prediction
1.41% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | libpulse-binding | <1.2.1 >=0.0.0-0, <1.2.1 |
1.2.1 |
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
github.com
/jnqnfe/pulse-binding-rust/commit/e6930e16573f0b6d12d6628ba5de59147d6f9e95
web
-
rustsec.org
/advisories/RUSTSEC-2018-0021.html
web, third-party-advisory, advisory
-
raw.githubusercontent.com
/rustsec/advisory-db/main/crates/libpulse-binding/RUSTSEC-2018-0021.md
web, third-party-advisory, us-government-resource
-
github.com
/jnqnfe/pulse-binding-rust/security/advisories/GHSA-ghpq-vjxw-ch5w
web
-
nvd.nist.gov
/vuln/detail/CVE-2018-25028
advisory
-
github.com
/jnqnfe/pulse-binding-rust
package
-
nvd.nist.gov
/vuln/detail/CVE-2018-25027
advisory
-
crates.io
/crates/libpulse-binding
package
Sources
- CVE List CVE-2018-25027
- GitHub Advisory GHSA-jqpv-jm4m-86j9
- GitHub Advisory GHSA-ghpq-vjxw-ch5w
- GitHub Advisory GHSA-hxjf-h2mh-r6hj
- NVD CVE-2018-25027
- OSV RUSTSEC-2018-0021
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.