PatchTheCVElibpulse-binding vulnerabilities and fixes
Recent CVEs affecting libpulse-binding, with upgrade or downgrade steps. 4 tracked.
Also searched as: libpulse binding.
libpulse-binding has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2021-12-27. Highest priority: CVE-2018-25027 (score 49/100).
- 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
- CVE-2018-25001 MEDIUM 6.5 UPGRADE An issue was discovered in the libpulse-binding crate before 2.5.0 for Rust
FAQ
How do I fix libpulse-binding vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is libpulse-binding being exploited right now?
None of the tracked libpulse-binding CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libpulse-binding CVE should I patch first?
CVE-2018-25027 currently ranks highest (49/100): An issue was discovered in the libpulse-binding crate before 1.2.1 for Rust.