CVE-2022-44732
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 Cyber Protect Home Office (Windows) before build 39900.
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 confidenceLocal privilege escalation vulnerability in Acronis Cyber Protect Home Office for Windows caused by insecure folder permissions. Attackers with low-privileged local access can exploit misconfigured permissions on certain folders to modify executable files or gain code execution with elevated (SYSTEM) privileges.
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< 39900CVSS 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.
-
Verify Acronis Cyber Protect Home Office is installedOpen Programs and Features or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Acronis*"}' to list installed Acronis productsAffected if Acronis Cyber Protect Home Office appears in the installed programs list
-
Check installed build versionLook in Programs and Features under the Version column, or check the installation directory for a version info file, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Acronis*"}'Affected if The build version number is less than 39900
-
Identify installation folderCheck the default installation path (typically C:\Program Files\Acronis\Cyber Protect Home Office\) or the path shown in the program's properties in Programs and FeaturesAffected if The program is installed in any directory on the system
-
Inspect folder permissions on executables directoryRight-click the main program folder, go to Security tab, click Advanced. Check if Users or Authenticated Users have Write or Modify permissions to folders containing .exe filesAffected if Non-privileged users have Write or Modify permissions on folders that contain executable files used by the protection service
The environment is affected if Acronis Cyber Protect Home Office is installed with a build version below 39900 AND non-admin users have write permissions on folders containing the program's executable files.
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 · scoped39900
Upgrade to Acronis Cyber Protect Home Office build 39900 or later to resolve the insecure folder permission vulnerability.
Cyber Protect Home Office build 39900 or later
- Upgrade Cyber Protect Home Office to build 39900 or later
- Verify the upgrade was successful by checking the installed version in the application's 'About' or 'Help' section
- Ensure the installed version shows build number 39900 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44732 — 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-44732 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