dbcve.org
Cyber Protect Home OfficeApplication · Acronis

CVE-2022-44733

HIGH · 7.8 CVSS v3.1 Published 2022-11-07
Fix available
A fix is available. Upgrade to 39900 or later.
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 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 confidence

Local privilege escalation vulnerability in Acronis Cyber Protect Home Office for Windows. The issue stems from insecure folder permissions that allow a local attacker to manipulate folder ACLs or replace executable files to gain elevated SYSTEM privileges. Exploitation requires local access to the target machine.

MitigationUpdate Acronis Cyber Protect Home Office to build 39900 or later. As an interim control, audit and harden folder permissions on the Acronis installation directories to prevent unauthorized modification by low-privileged users.

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
Cyber Protect Home OfficeApplication
Affected:< 39900

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. Verify Acronis Cyber Protect Home Office is installed
    Open Programs and Features (appwiz.cpl) or check for Acronis installation in C:\Program Files\Acronis or C:\Program Files (x86)\Acronis
    Affected if The software is not found, the CVE does not apply
  2. Determine installed build version
    Run 'agent --version' from the Acronis installation directory, or right-click the Acronis executable in Task Manager and select Properties > Details to view the File Version
    Affected if Unable to retrieve version information, manual inspection required
  3. Compare build number to affected range
    Check if the installed build number is less than 39900. The affected version range is any build below 39900
    Affected if Build number is below 39900, indicating the vulnerable version is installed
  4. Inspect Acronis installation folder permissions
    Right-click the Acronis installation folder (typically in Program Files), select Properties > Security, and verify which users have Write or Modify permissions
    Affected if Low-privileged users (such as Users or Authenticated Users) have Write or Modify permissions on Acronis folders, enabling exploitation of the ACL manipulation vector

A user is affected if Acronis Cyber Protect Home Office is installed with a build number below 39900 AND low-privileged accounts have write access to the Acronis installation directories.

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
Upgrade available Upgrade to 39900 or later
Fixed in 39900
Interim mitigation

Update Acronis Cyber Protect Home Office to build 39900 or later. As an interim control, audit and harden folder permissions on the Acronis installation directories to prevent unauthorized modification by low-privileged users.

Recommended fix Moderate confidence

Cyber Protect Home Office (Windows) build 39900 or later

  1. Verify current installed version of Acronis Cyber Protect Home Office by opening the application and checking About or Help > About
  2. Download the latest version of Acronis Cyber Protect Home Office from the official Acronis website or trusted distribution channel
  3. Close any running instances of the Acronis Cyber Protect Home Office application
  4. Run the installer with appropriate privileges
  5. Follow the on-screen prompts to complete the installation
  6. Verify the installed build number is 39900 or later after installation completes
  7. Restart the system if prompted or required by the installer

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

Fix this in Cyber Protect Home Office Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44733 — 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-44733 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