Local privilege escalation via improperly protected named pipe
Published Feb 4, 2022 · Updated Sep 17, 2024
Local privilege escalation in four Acronis Windows products allows local users to gain elevated privileges through a named pipe. The affected software performs improper access-control checks on a named pipe used to communicate with a privileged process. Exploitation requires existing high privileges and user interaction, and successful abuse permits control over protected data and services.
Summary
What happened
Local privilege escalation in four Acronis Windows products allows local users to gain elevated privileges through a named pipe. The affected software performs improper access-control checks on a named pipe used to communicate with a privileged process. Exploitation requires existing high privileges and user interaction, and successful abuse permits control over protected data and services.
The record
- CVE
- CVE-2021-44204
- Published
- Feb 4, 2022
- Updated
- Sep 17, 2024
- Vendor
- Acronis
- Product
- Acronis True Image
- Classifications
- CWE-285, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 4, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <39287
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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