Skip to content
Fencer Intel
high 8.1

CVE-2020-7040 json

storeBackup.pl in storeBackup through 3.5 relies on the /tmp/storeBackup.lock pathname, which allows symlink attacks that possibly lead to…

published 6y ago modified 4mo ago also EUVD-2020-28174

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.9%
EPSS 2.9% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

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

Patch / fix

  • storebackup Debian 14, Debian 13, Debian 12 3.2.1-2

debian advisories DEBIAN-CVE-2020-7040

  • storebackup Ubuntu 16.04 LTS 3.2.1-1+deb8u1build0.16.04.1
  • storebackup Ubuntu 18.04 LTS 3.2.1-1+deb8u1build0.18.04.1
  • storebackup Ubuntu 20.04 LTS 3.2.1-1+deb8u1build0.20.04.1

ubuntu advisories UBUNTU-CVE-2020-7040

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • storeBackup openSUSE Tumbleweed 3.5-13.2
  • storeBackup Package Hub 15 SP1, Package Hub 15, openSUSE Leap 15.1 3.5-bp151.4.3.1

opensuse advisories openSUSE-SU-2024:11410-1openSUSE-SU-2020:0119-1

Is CVE-2020-7040 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.87% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.