CWE
59
Advisory Published
CVE Published
Updated

CVE-2020-7040

First published: Tue Jan 21 2020(Updated: )

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

Credit: cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
ubuntu/storebackup<3.2.1-1+
3.2.1-1+
ubuntu/storebackup<3.2.1-1+
3.2.1-1+
ubuntu/storebackup<3.2.1-1+
3.2.1-1+
debian/storebackup
3.2.1-2
storeBackup storeBackup<=3.5
Debian=8.0
openSUSE Backports=15.0
openSUSE Backports=15.0-sp1
openSUSE=15.1
Ubuntu=16.04
Ubuntu=18.04
Ubuntu=20.04

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2020-7040?

    CVE-2020-7040 is categorized as a high severity vulnerability due to its potential for privilege escalation via symlink attacks.

  • How do I fix CVE-2020-7040?

    To fix CVE-2020-7040, upgrade the storeBackup package to version 3.5 or higher.

  • Which versions of storeBackup are affected by CVE-2020-7040?

    Versions of storeBackup up to and including 3.5 are affected by CVE-2020-7040.

  • Can local users exploit CVE-2020-7040?

    Yes, local users can exploit CVE-2020-7040 by creating a symlink to the /tmp/storeBackup.lock pathname.

  • What impact does CVE-2020-7040 have on system security?

    CVE-2020-7040 can lead to privilege escalation, allowing attackers to gain unauthorized access to system resources.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203