Upstream information

CVE-2020-7040 at MITRE

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

SUSE information

Overall state of this security issue: Resolved

This issue is currently rated as having critical severity.

CVSS v2 Scores
  National Vulnerability Database
Base Score 9.3
Vector AV:N/AC:M/Au:N/C:C/I:C/A:C
Access Vector Network
Access Complexity Medium
Authentication None
Confidentiality Impact Complete
Integrity Impact Complete
Availability Impact Complete
CVSS v3 Scores
  National Vulnerability Database
Base Score 8.1
Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector Network
Attack Complexity High
Privileges Required None
User Interaction None
Scope Unchanged
Confidentiality Impact High
Integrity Impact High
Availability Impact High
CVSSv3 Version 3.1
SUSE Bugzilla entries: 1150555 [RESOLVED / FIXED], 1156767 [IN_PROGRESS]

SUSE Security Advisories:

List of released packages

Product(s) Fixed package version(s) References
SUSE Package Hub 15 SP1
  • storeBackup >= 3.5-bp151.4.3.1
SUSE Package Hub 15
  • storeBackup >= 3.5-bp150.3.3.1
openSUSE Leap 15.1
  • storeBackup >= 3.5-lp151.5.3.1
openSUSE Tumbleweed
  • storeBackup >= 3.5-13.2
openSUSE Tumbleweed GA storeBackup-3.5-13.2

SUSE Timeline for this CVE

CVE page created: Wed Jan 15 10:04:20 2020
CVE page last modified: Tue May 23 15:30:40 2023