CVE-2017-8418 · cross-distro fix matrix

CVE-2017-8418: RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with cache files belonging to other users.

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

Fix per ecosystem

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

Debian bullseye

Source: Debian Security Tracker

rubocop→ fixed in0.49.1+dfsg-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y rubocop
```

Debian bookworm

Source: Debian Security Tracker

rubocop→ fixed in0.49.1+dfsg-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y rubocop
```

Debian trixie

Source: Debian Security Tracker

rubocop→ fixed in0.49.1+dfsg-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y rubocop
```

Are YOU affected by CVE-2017-8418?

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-2017-8418dropped 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)