dbcve.org
Cyber Protect Home OfficeApplication · Acronis

CVE-2022-44746

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-07
Fix available
A fix is available. Upgrade to 40107 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Sensitive information disclosure due to insecure folder permissions. The following products are affected: Acronis Cyber Protect Home Office (Windows) before build 40107.

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

Acronis Cyber Protect Home Office for Windows prior to build 40107 contains insecure folder permissions that allow local attackers to access sensitive information. The vulnerability stems from improper access control lists (ACLs) on application folders, potentially exposing configuration files, credentials, or other sensitive data to unauthorized users.

MitigationUpgrade to Acronis Cyber Protect Home Office build 40107 or later. Alternatively, audit and restrict folder permissions on the application directory to enforce least-privilege access controls.

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:< 40107

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Acronis Cyber Protect Home Office installation
    Open Programs and Features (appwiz.cpl) or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Acronis Cyber Protect Home Office' or similar Acronis product
    Affected if The product is not listed or no Acronis installation is found, the system is not affected by this specific vulnerability
  2. Identify installed build version
    Right-click the Acronis Cyber Protect Home Office application in Programs and Features, select Properties, and view the Version field; alternatively, launch the application and check Help > About for the full build number
    Affected if The build number is less than 40107 (for example, 40000, 39500, etc.), indicating the vulnerable version is installed
  3. Locate the application installation directory
    Right-click the Acronis entry in Programs and Features and select Properties to find the Install Location path, or check the registry key identified in step 1 for the InstallLocation value
    Affected if An installation directory path is found pointing to an Acronis program folder
  4. Inspect folder permissions on the application directory
    Right-click the Acronis installation folder identified in step 3, select Properties, go to the Security tab, and review the list of users/groups with access; use 'icacls <folderpath>' from an elevated command prompt for detailed ACL output
    Affected if Users other than Administrators, SYSTEM, or the installing user have Full Control, Modify, or Read & Execute permissions to sensitive subfolders containing configuration, credentials, or log files

The system is affected if Acronis Cyber Protect Home Office is installed with a build number lower than 40107 AND the application folder has overly permissive ACLs allowing unauthorized local users access to sensitive data.

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 40107 or later
Fixed in 40107
Interim mitigation

Upgrade to Acronis Cyber Protect Home Office build 40107 or later. Alternatively, audit and restrict folder permissions on the application directory to enforce least-privilege access controls.

Recommended fix High confidence

Acronis Cyber Protect Home Office build 40107 or later

  1. Check current installed version of Acronis Cyber Protect Home Office
  2. Upgrade to build 40107 or later of Acronis Cyber Protect Home Office (Windows)
  3. Verify the upgrade was successful and version is 40107 or higher

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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