CVE-2022-45452
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 folder permissions. The following products are affected: Acronis Agent (Windows) before build 30430, 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 confidenceLocal privilege escalation vulnerability in Acronis Agent and Cyber Protect 15 Windows versions due to insecure folder permissions. Low-privileged users can modify protected folders to gain elevated (SYSTEM) privileges. Fixed in builds 30430 (Agent) and 30984 (Cyber Protect 15).
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< c21.09< 15= 15CVSS 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 Acronis product installationOpen Windows Services (services.msc) and look for services starting with 'Acronis' or check Programs and Features for Acronis Agent or Acronis Cyber Protect 15Affected if Either Acronis Agent or Acronis Cyber Protect 15 is installed
-
Determine installed build versionRun 'Get-ItemProperty' on the registry key 'HKLM\SOFTWARE\Acronis\Global' or check the About dialog in the Acronis management console for the exact build numberAffected if The build number is below 30430 for Agent or below 30984 for Cyber Protect 15
-
Locate Acronis protected directoriesCheck the installation directory (typically C:\Program Files\Acronis\ or C:\Program Files (x86)\Acronis\) and identify subdirectories used for backups, catalogs, or storageAffected if Protected directories exist in the Acronis installation path
-
Inspect folder permissions on protected directoriesRight-click each protected folder, go to Properties > Security tab, and verify that Users or Authenticated Users have only Read/Execute permissions, not Write or Full ControlAffected if Low-privileged users (such as standard users or the 'Users' group) have Write or Full Control permissions to folders that should be protected
You are affected if Acronis Agent build is below 30430 or Cyber Protect 15 build is below 30984, OR if low-privileged users have Write access to Acronis protected folders regardless of version.
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 · scoped15
Update Acronis Agent to build 30430 or later, and Acronis Cyber Protect 15 to build 30984 or later. Verify folder permissions restrict write access to protected directories.
Acronis Agent c21.09 (build 30430+) or Acronis Cyber Protect 15 build 30984+
- Identify the currently installed Acronis Agent or Acronis Cyber Protect 15 version on the Windows system
- Navigate to the Acronis product management console or use the installed client to check the current build number
- For Acronis Agent: Upgrade to version c21.09 or later (build 30430 or higher)
- For Acronis Cyber Protect 15: Upgrade to build 30984 or later
- Verify the upgrade was successful by checking the new build number matches or exceeds the fixed versions
- Confirm that folder permissions on the Acronis installation directories have been properly hardened
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45452 — 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-45452 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