CVE-2020-7040 · cross-distro fix matrix

CVE-2020-7040: storeBackup.pl in storeBackup through 3.5 relies on the /tmp/storeBackup.lock pathname, which allows symlink attacks that possibly lead to privilege escalation. (Local users can also create a plain file named /tmp/storeBackup.lock to block use of storeBackup until an admin manually deletes that file

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

Fix per ecosystem

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

Debian bullseye

Source: Debian Security Tracker

storebackup→ fixed in3.2.1-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y storebackup
```

Debian bookworm

Source: Debian Security Tracker

storebackup→ fixed in3.2.1-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y storebackup
```

Debian trixie

Source: Debian Security Tracker

storebackup→ fixed in3.2.1-2urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y storebackup
```

Are YOU affected by CVE-2020-7040?

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-2020-7040dropped 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)