CVE-2022-45454
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 · uneditedSensitive information disclosure due to insecure folder permissions. The following products are affected: Acronis Agent (Windows) before build 30161, 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 confidenceSensitive information disclosure vulnerability in Acronis Agent and Cyber Protect 15 for Windows caused by insecure folder permissions. The affected versions (Acronis Agent before build 30161 and Cyber Protect 15 before build 30984) have folder permissions that allow unauthorized users to access potentially sensitive data stored in application directories.
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.08= 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 productOpen Windows Registry and check for Acronis entries under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Acronis*'}Affected if Neither Acronis Agent nor Cyber Protect 15 is found on the system, then the CVE does not apply
-
Determine Acronis Agent versionCheck the installed version of Acronis Agent - look for the build number (c22.08 corresponds to build 30161). Check in Windows Registry under HKLM\SOFTWARE\Acronis\ or examine the executable version properties of the installed agent componentsAffected if The installed build number is less than 30161 (versions before c22.08)
-
Determine Cyber Protect 15 versionCheck the installed version of Cyber Protect 15 - verify the build number (build 30984 is the fixed version). Check in Windows Registry or examine the executable version properties of Cyber Protect componentsAffected if Cyber Protect 15 is installed with a build number lower than 30984
-
Inspect folder permissions on Acronis directoriesExamine the security permissions on the Acronis installation directory (typically C:\Program Files\Acronis or C:\ProgramData\Acronis). Use icacls or right-click Properties > Security to check if non-admin users or the Users group have excessive read or write access to sensitive subdirectoriesAffected if Non-privileged users or the Users group have Read, Write, or Modify permissions on directories containing sensitive backup or configuration data
-
Verify sensitive data accessibilityAttempt to access Acronis data directories using a standard non-privileged Windows account or check if the directory ACLs permit access from the Users or Authenticated Users groups. Look at folders containing backup images, configuration files, or encryption keysAffected if A standard user account (non-admin) can read or list contents of directories that should contain sensitive Acronis data such as backups, credentials, or encryption keys
The system is affected if either Acronis Agent before build 30161 or Cyber Protect 15 before build 30984 is installed AND the Acronis program directories have overly permissive ACLs allowing unauthorized access to sensitive data.
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 · scopedUpdate to Acronis Agent build 30161 or higher, and Cyber Protect 15 build 30984 or higher. Additionally, review and harden folder permissions on affected systems to ensure only authorized users and processes can access Acronis data directories.
Acronis Agent (Windows) build 30161 or later; Acronis Cyber Protect 15 (Windows) build 30984 or later
- 1. Identify the current build version of Acronis Agent or Cyber Protect 15 installed on the Windows system
- 2. For Acronis Agent: If the current build is below 30161, upgrade to build 30161 or later
- 3. For Acronis Cyber Protect 15: If the current build is below 30984, upgrade to build 30984 or later
- 4. Verify the upgrade was successful by checking the new build number in the product UI or via command line
- 5. Confirm that folder permissions on sensitive directories have been hardened after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45454 — 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-45454 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