CVE-2020-7040: storeBackup.pl in storeBackup through 3.5 relies on the /tmp/storeBackup.lock pathname, which allows symlink a

This week

HIGH 8.1REMOTEWATCHLISTUPGRADEMITIGATEDOWNGRADE

CVE-2020-7040 is a high-severity flaw (CVSS 8.1) affecting storebackup, debian linux, backports sle. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.)

Why this priority

High severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	2.9% (top 13%)
CISA exploited list	No
Weakness	CWE-59
Published	2020-01-21
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: canonical · debian · opensuse · storebackup

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-01-21 21:15 UTCPublished CVE record published
2026-06-17 03:24 UTCUpdated Record last modified

storebackup storebackup UPGRADE

Affected: <= 3.5

Fixed in: newer than 3.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy storebackup || rpm -q storebackup || storebackup --version

2. UPGRADE to newer than 3.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade storebackup

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade storebackup

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

debian debian linux MITIGATE

Affected: 8.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 8.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

opensuse backports sle DOWNGRADE

Affected: 15.0 · 15.0 sp1

Fixed in: no fixed release known

Safe to downgrade to: a release before 15.0

1. Check installed version

apt-cache policy backports-sle || rpm -q backports-sle || backports-sle --version

2. No fixed release: DOWNGRADE to a release before 15.0 (Debian / Ubuntu)

apt-cache madison backports-sle sudo apt install backports-sle=<VERSION_BEFORE_15.0> sudo apt-mark hold backports-sle

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list backports-sle sudo dnf downgrade backports-sle-<VERSION_BEFORE_15.0> sudo dnf versionlock add backports-sle

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

opensuse leap MITIGATE

Affected: 15.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 15.1

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

canonical ubuntu linux MITIGATE

Affected: 16.04 · 18.04 · 20.04

Fixed in: no fixed release known

Safe to downgrade to: a release before 16.04

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-7040?

storebackup: upgrade to newer than 3.5; debian linux: mitigate or apply the listed mitigation; backports sle: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-7040 being exploited?

CVE-2020-7040 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-7040 affect?

CVE-2020-7040 affects storebackup, debian linux, backports sle. Severity is high (CVSS 8.1). 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

How urgent is CVE-2020-7040?

Priority 60/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Ubuntu vulnerabilities · Debian vulnerabilities

References

← Back to latest CVEs