Storebackup is a niche backup utility focused on file-system archival and recovery, with its documented exposure centered on the core product itself. The recurring vulnerability signal reflects symlink-traversal and improper link-resolution issues, typical of backup tools that must carefully manage file-access semantics during archive operations. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Storebackup over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-7040HIGH 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 al | Jan 21, 2020 | 8.1 | 23 | NO | NO |
CVE-2005-3148MEDIUM StoreBackup before 1.19 does not properly set the uid and guid for symbolic links (1) that are backed up by storeBackup.pl, or (2) recovered by storeBackupRecover.pl, which could c | Oct 5, 2005 | 4.6 | 14 | NO | NO |
StoreBackup before 1.19 allows local users to perform unauthorized operations on arbitrary files via a symlink attack on temporary files. | Oct 5, 2005 | 2.1 | 11 | NO | NO |
StoreBackup before 1.19 creates the backup root with world-readable permissions, which allows local users to obtain sensitive information. | Oct 5, 2005 | 2.1 | 11 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Storebackup.
Media articles that mention a CVE ID that affects a product developed by Storebackup — matched by CVE ID, not by vendor name.