Local privilege escalation via lock-file symlink race
Published Jan 21, 2020 · Updated Aug 4, 2024
Symlink race in storeBackup through 3.5 allows local users to overwrite files or escalate privileges through a fixed lock-file path. storeBackup.pl calls stat() and then lstat() on /tmp/storeBackup.lock before opening the pathname for creation, leaving a race in which a symlink redirects a root-run write. The program typically runs as root; a plain file at the same path also makes backup jobs exit immediately, causing a local service interruption.
Summary
What happened
Symlink race in storeBackup through 3.5 allows local users to overwrite files or escalate privileges through a fixed lock-file path. storeBackup.pl calls stat() and then lstat() on /tmp/storeBackup.lock before opening the pathname for creation, leaving a race in which a symlink redirects a root-run write. The program typically runs as root; a plain file at the same path also makes backup jobs exit immediately, causing a local service interruption.
The record
- CVE
- CVE-2020-7040
- Published
- Jan 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-59, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Plain lock-file denial-of-service proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo