RUSTSEC-2020-0055

Please see RUSTSEC-2018-0020

Not rated yet Withdrawn Oct 22, 2020 crates.io

Severity: Not rated yet; No source has published a CVSS score yet
Exploit chance (EPSS): —; No score published
Known exploited: No; Not in CISA's catalog
Weakness: —; Not classified
Fix: 0.0.1-0; Upgrade libpulse-binding to this version or later

Description

This vulnerability was misfiled under the wrong year and has been withdrawn.

Affected versions

crates.io

Package	Vulnerable	Fixed in
libpulse-binding	`>= 0.0.0-0, < 0.0.1-0`	`0.0.1-0`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

libpulse-binding crates.io → `0.0.1-0`

cargo

cargo update -p libpulse-binding --precise 0.0.1-0

References

Advisories

Packages

crates.io/crates/libpulse-binding

Timeline

Oct 21, 2020 Published
Oct 22, 2020 Withdrawn
Aug 16, 2022 Last updated by the source

Advisory	Severity	Why it's related
GHSA-wcxc-jf6c-8rx9 Duplicate Advisory: Uncaught Exception in libpulse-binding	High	Also affects libpulse-binding
GHSA-6gvc-4jvj-pwq4 Duplicate Advisory: Use after free in libpulse-binding	Medium	Also affects libpulse-binding
GHSA-jqpv-jm4m-86j9 Use after free in libpulse-binding	High	Also affects libpulse-binding

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor