CVE-2019-12300: Improper Authentication in Buildbot

CVE-2019-12300 · Severity: low · CVSS 3 · Published 2019-05-23

Buildbot before 1.8.2 and 2.x before 2.3.1 accepts a user-submitted authorization token from OAuth and uses it to authenticate a user. If an attacker has a token allowing them to read the user details of a victim, they can login as the victim.

Technologies: buildbot (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2019-12300 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-12300 being exploited in the wild.
How severe is CVE-2019-12300?
Low severity, with a CVSS score of 3, published 23 May 2019.
Which products and versions are affected?
buildbot (PyPI) ECOSYSTEM:introduced=0,fixed=1.8.2, ECOSYSTEM:introduced=0,fixed=1.8.2,introduced=2.0.1,fixed=2.3.1.
Is there a fix for CVE-2019-12300?
Yes. buildbot (PyPI): upgrade to 1.8.2, 2.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-12300?
Check whether you run buildbot (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

  • buildbot (PyPI): upgrade to 1.8.2, 2.3.1 or later
    pip install "buildbot>=2.3.1"

Affected products

  • buildbot (PyPI) ECOSYSTEM:introduced=0,fixed=1.8.2, ECOSYSTEM:introduced=0,fixed=1.8.2,introduced=2.0.1,fixed=2.3.1

Identifiers

  • CVE-2019-12300
  • GHSA-g86p-hgx5-2pfh
  • PYSEC-2019-6

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