CVE-2022-45451
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 · uneditedLocal privilege escalation due to insecure driver communication port permissions. The following products are affected: Acronis Cyber Protect Home Office (Windows) before build 40173, Acronis Agent (Windows) before build 30600, 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 · high confidenceAcronis Windows products ship with a kernel-mode driver that exposes a communication port for inter-process messaging. This port was configured with insufficient access controls, allowing any local user to send privileged commands to the driver and execute code at SYSTEM privilege level, achieving local privilege escalation.
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< c22.10= 15< 40173CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Acronis productsOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject Win32_Product' or check registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Acronis entriesAffected if Acronis Agent, Acronis Cyber Protect 15, or Acronis Cyber Protect Home Office is listed as installed
-
Determine Acronis Agent versionCheck the installed version through Acronis management console, registry key, or by querying the Acronis ServiceAffected if Version string is below c22.10 or numeric build below 30600
-
Determine Acronis Cyber Protect 15 versionCheck the installed version through Acronis management console, registry, or installed programs listAffected if Acronis Cyber Protect 15 is present (all versions of build 15 are affected)
-
Determine Acronis Cyber Protect Home Office versionCheck the installed version through the application or installed programs listAffected if Version is below build 40173
A system is affected if any Acronis product is installed with a version matching the vulnerable ranges: Acronis Agent < c22.10/30600, Acronis Cyber Protect 15 any version, or Acronis Cyber Protect Home Office < 40173.
Generated from the published advisory. Verify against your own configuration.
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 · scoped40173
Update Acronis Cyber Protect Home Office to build 40173 or later, Acronis Agent to build 30600 or later, and Acronis Cyber Protect 15 to build 30984 or later to obtain patched driver with proper port permissions.
Acronis Cyber Protect Home Office: build 40173+ | Acronis Agent: build 30600+ (c22.10) | Acronis Cyber Protect 15: build 30984+
- 1. Identify the installed Acronis product (Agent, Cyber Protect 15, or Cyber Protect Home Office) and current build version
- 2. For Acronis Cyber Protect Home Office: Upgrade to build 40173 or later
- 3. For Acronis Agent: Upgrade to build 30600 (c22.10) or later
- 4. For Acronis Cyber Protect 15: Upgrade to build 30984 or later
- 5. Verify the upgrade was successful by checking the build number in the product UI or About section
- 6. Restart the system if prompted to ensure the new driver with proper permissions is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45451 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45451 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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