CVE-2019-12300 · cross-distro fix matrix

CVE-2019-12300: 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.

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2019-12300 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

buildbot→ fixed in2.0.1-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y buildbot
```

Debian bookworm

Source: Debian Security Tracker

buildbot→ fixed in2.0.1-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y buildbot
```

Debian trixie

Source: Debian Security Tracker

buildbot→ fixed in2.0.1-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y buildbot
```

Are YOU affected by CVE-2019-12300?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2019-12300dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)