dbcve.org
AgentApplication · Acronis

CVE-2022-45455

HIGH · 7.8 CVSS v3.1 Published 2023-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Local privilege escalation due to incomplete uninstallation cleanup. The following products are affected: Acronis Cyber Protect Home Office (Windows) before build 40107, Acronis Agent (Windows) before build 30025, Acronis Cyber Protect 15 (Windows) before build 30984.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Local privilege escalation vulnerability in Acronis Windows products caused by incomplete uninstallation cleanup. When the software is uninstalled, certain components, files, or service configurations are not properly removed, leaving artifacts that can be exploited by a local attacker to gain elevated (SYSTEM/Administrator) privileges on the affected Windows system.

MitigationUpdate to the fixed builds: Acronis Cyber Protect Home Office to build 40107 or later, Acronis Agent to build 30025 or later, and Acronis Cyber Protect 15 to build 30984 or later. For already-affected systems, manual cleanup of residual files and service entries may be required in addition to updating.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AgentApplication
Affected:< c22.07
Cyber ProtectApplication
Affected:= 15
Cyber Protect Home OfficeApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check for residual Acronis Windows services
    Open Services.msc or run 'sc query' in Command Prompt and look for any service entries containing 'Acronis' that remain after uninstallation.
    Affected if Any Acronis-related service entries exist on the system after the product has been uninstalled.
  2. Inspect Acronis program directories for leftover files
    Check typical Acronis installation paths such as C:\Program Files\Acronis, C:\Program Files (x86)\Acronis, and %ProgramData%\Acronis for any remaining files or folders.
    Affected if Any Acronis directories or files persist after the software has been uninstalled.
  3. Review scheduled tasks for Acronis entries
    Open Task Scheduler and look under Task Scheduler Library for any Acronis-related scheduled tasks, or run 'schtasks /query /fo LIST' and search for Acronis entries.
    Affected if Any Acronis scheduled tasks remain on the system after uninstallation.
  4. Check registry for Acronis uninstall entries
    Review the registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Acronis product entries, and check HKLM\SYSTEM\CurrentControlSet\Services for Acronis service keys.
    Affected if Registry entries for Acronis services or uninstall information remain after the product has been removed.

If any Acronis components (services, files, scheduled tasks, or registry entries) remain on the system after uninstallation, the incomplete cleanup vulnerability is present and could allow local privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the fixed builds: Acronis Cyber Protect Home Office to build 40107 or later, Acronis Agent to build 30025 or later, and Acronis Cyber Protect 15 to build 30984 or later. For already-affected systems, manual cleanup of residual files and service entries may be required in addition to updating.

Recommended fix High confidence

Acronis Agent: build 30025+ (c22.07+); Acronis Cyber Protect 15: build 30984+; Acronis Cyber Protect Home Office: build 40107+

  1. 1. Identify the installed Acronis product (Agent, Cyber Protect 15, or Cyber Protect Home Office) on the affected Windows system
  2. 2. Check the current build version of the installed Acronis software
  3. 3. For Acronis Agent: upgrade to build 30025 or later (c22.07 or newer)
  4. 4. For Acronis Cyber Protect 15: upgrade to build 30984 or later
  5. 5. For Acronis Cyber Protect Home Office: upgrade to build 40107 or later
  6. 6. Verify the upgrade was successful by checking the new build version
  7. 7. Confirm the vulnerability is remediated by verifying the build number meets or exceeds the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45455 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45455 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data