CVE-2018-25027: RUSTSEC-2018-0021 - Use-after-free with objects returned by `Stream`'s `get_format_info` and `get_context` methods

CVE-2018-25027 · Severity: low · CVSS 3.1 · Published 2018-06-15

Use-after-free with objects returned by `Stream`'s `get_format_info` and `get_context` methods

Technologies: libpulse-binding (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2018-25027 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-25027 being exploited in the wild.
How severe is CVE-2018-25027?
Low severity, with a CVSS score of 3.1, published 15 June 2018.
Which products and versions are affected?
libpulse-binding (crates.io) SEMVER:introduced=0,fixed=1.2.1, SEMVER:introduced=0.0.0-0,fixed=1.2.1.
Is there a fix for CVE-2018-25027?
Yes. libpulse-binding (crates.io): upgrade to 1.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-25027?
Check whether you run libpulse-binding (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • libpulse-binding (crates.io): upgrade to 1.2.1 or later
    cargo update -p libpulse-binding

Affected products

  • libpulse-binding (crates.io) SEMVER:introduced=0,fixed=1.2.1, SEMVER:introduced=0.0.0-0,fixed=1.2.1

Identifiers

  • CVE-2018-25027
  • CVE-2018-25028
  • GHSA-ghpq-vjxw-ch5w
  • GHSA-hxjf-h2mh-r6hj
  • GHSA-jqpv-jm4m-86j9
  • RUSTSEC-2018-0021

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.