CVE-2016-3180 · cross-distro fix matrix

CVE-2016-3180: Tor Browser Launcher (aka torbrowser-launcher) before 0.2.4, during the initial run, allows man-in-the-middle attackers to bypass the PGP signature verification and execute arbitrary code via a Trojan horse tar file and a signature file with the valid tarball and signature.

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

Fix per ecosystem

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

Debian bullseye

Source: Debian Security Tracker

torbrowser-launcher→ fixed in0.2.4-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y torbrowser-launcher
```

Debian bookworm

Source: Debian Security Tracker

torbrowser-launcher→ fixed in0.2.4-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y torbrowser-launcher
```

Debian trixie

Source: Debian Security Tracker

torbrowser-launcher→ fixed in0.2.4-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y torbrowser-launcher
```

Are YOU affected by CVE-2016-3180?

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-2016-3180dropped 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)