Persistent service crash via predictable log hardlink
Published May 25, 2021 · Updated Aug 4, 2024
Denial of service in Acronis True Image 2020 24.5.22510 allows local users to crash anti_ransomware_service.exe after reboot. The service writes predictably named logs in a user-writable Active Protection directory without preventing a hardlink to its executable. A low-privileged local user can plant the next log-name hardlink; each reboot then triggers a sharing violation and leaves ransomware protection stopped.
Summary
What happened
Denial of service in Acronis True Image 2020 24.5.22510 allows local users to crash anti_ransomware_service.exe after reboot. The service writes predictably named logs in a user-writable Active Protection directory without preventing a hardlink to its executable. A low-privileged local user can plant the next log-name hardlink; each reboot then triggers a sharing violation and leaves ransomware protection stopped.
The record
- CVE
- CVE-2020-9451
- Published
- May 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276, T1489
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 25, 2021CVE 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.
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.
Public exploit references
- Predictable log-name hardlink denial-of-service procedurefunctional · 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