# CVE-2019-12300: Improper Authentication in Buildbot

> Attackers can log in as victims by submitting stolen OAuth tokens, leading to account takeover in Buildbot.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-12300, GHSA-g86p-hgx5-2pfh, PYSEC-2019-6, UBUNTU-CVE-2019-12300

## What is CVE-2019-12300?

CVE-2019-12300 is a critical authentication bypass vulnerability in n/a, published on 23 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-12300?

5 open source packages ship an affected version, including buildbot. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `buildbot` | PyPI | All versions | 1.8.2, 2.3.1 |
| `buildbot` | PyPI | All versions | 1.8.2 |
| `buildbot` | PyPI | All versions | 1.8.2 |
| `buildbot` | PyPI | From 2.0.0 | 2.3.1 |
| `buildbot` | PyPI | From 2.0.0 | 2.3.1 |

Products: Buildbot Buildbot.

## How do I fix CVE-2019-12300?

Upgrade buildbot to a fixed version for your release line: 1.8.2 or 2.3.1.

## Is CVE-2019-12300 being exploited?

There is no known exploitation of CVE-2019-12300 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-7313](https://insights.sbomify.com/CVE-2019-7313/): Buildbot CRLF Injection (medium 6.1)
- [CVE-2009-2967](https://insights.sbomify.com/CVE-2009-2967/): Buildbot vulnerable to cross-site scripting (medium 4.3)
- [CVE-2009-2959](https://insights.sbomify.com/CVE-2009-2959/): Buildbot Cross-site scripting (XSS) vulnerability (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12300 and fix it if it is affected.

What it is: CVE-2019-12300 is a critical authentication bypass vulnerability in n/a, published on 23 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12300 in the wild and no public exploit code.

Affected packages and fixed versions:
- buildbot (PyPI): affected all versions; fixed in 1.8.2, 2.3.1
- buildbot (PyPI): affected all versions; fixed in 1.8.2
- buildbot (PyPI): affected all versions; fixed in 1.8.2
- buildbot (PyPI): affected from 2.0.0; fixed in 2.3.1
- buildbot (PyPI): affected from 2.0.0; fixed in 2.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-12300/ (Markdown: https://insights.sbomify.com/CVE-2019-12300/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-12300
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-12300
- OSV: https://osv.dev/vulnerability/CVE-2019-12300

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-12300/
Summaries are generated and may contain mistakes; the official description above is the record.