CVE-2018-1000132: Mercurial Incorrect Access Control vulnerability

CVE-2018-1000132 · Severity: low · CVSS 3 · Published 2018-03-14

Mercurial version 4.5 and earlier contains a Incorrect Access Control (CWE-285) vulnerability in Protocol server that can result in Unauthorized data access. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 4.5.1.

Technologies: mercurial (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2018-1000132 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-1000132 being exploited in the wild.
How severe is CVE-2018-1000132?
Low severity, with a CVSS score of 3, published 14 March 2018.
Which products and versions are affected?
mercurial (PyPI) ECOSYSTEM:introduced=0,fixed=4.5.1.
Is there a fix for CVE-2018-1000132?
Yes. mercurial (PyPI): upgrade to 4.5.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-1000132?
Check whether you run mercurial (PyPI) 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

  • mercurial (PyPI): upgrade to 4.5.1 or later
    pip install "mercurial>=4.5.1"

Affected products

  • mercurial (PyPI) ECOSYSTEM:introduced=0,fixed=4.5.1

Identifiers

  • CVE-2018-1000132
  • GHSA-4mr4-7vjv-9hm6
  • PYSEC-2018-87

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