dbcve.org
Cyber Protect Home OfficeApplication · Acronis

CVE-2022-44745

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 leak through log files. 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

Sensitive information may be written to log files in Acronis Cyber Protect Home Office for Windows prior to build 40107, potentially exposing confidential data to unauthorized parties with access to those log files.

MitigationUpgrade Acronis Cyber Protect Home Office to build 40107 or later to remediate the log file information disclosure. Review existing log files for any exposed sensitive information.

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 is installed
    Open Programs and Features in Windows Control Panel and look for 'Acronis Cyber Protect Home Office' in the installed programs list, or check the installation directory typically at C:\Program Files\Acronis\Cyber Protect Home Office\
    Affected if Acronis Cyber Protect Home Office is present on the system
  2. Determine the installed build version
    Right-click the Acronis Cyber Protect Home Office icon or executable, select Properties, then go to the Details tab to view the Product version, or open the application and navigate to Help > About to see the build number
    Affected if The build version shown is less than 40107
  3. Locate log files created by the application
    Check default log directories such as C:\ProgramData\Acronis\Cyber Protect Home Office\Logs\ or %USERPROFILE%\AppData\Local\Acronis\Cyber Protect Home Office\Logs\ for .log files
    Affected if Log files exist and were created prior to upgrading to build 40107 or later
  4. Review log file contents for sensitive data
    Open the log files found in the log directories using a text editor and search for patterns that may indicate sensitive information such as passwords, tokens, credentials, or personal data
    Affected if Log files contain any usernames, passwords, API keys, or other confidential data that should not be exposed

The environment is affected if Acronis Cyber Protect Home Office is installed with a build version lower than 40107, as sensitive information may have been written to accessible log files.

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 Acronis Cyber Protect Home Office to build 40107 or later to remediate the log file information disclosure. Review existing log files for any exposed sensitive information.

Recommended fix High confidence

Acronis Cyber Protect Home Office build 40107 (Windows)

  1. Locate the Acronis Cyber Protect Home Office installation on the affected Windows system
  2. Open the application's control panel or system tray interface
  3. Navigate to the Settings or Help section
  4. Check the current build number (Help > About)
  5. If the build number is below 40107, initiate an update check or download the latest version from the official Acronis website
  6. Apply the update to upgrade to build 40107 or later
  7. After updating, verify the new build number reflects 40107 or higher
  8. Review any new log files generated after the update to confirm sensitive information is no longer being logged
Caveat Review release notes for build 40107 for any functionality changes or migration requirements

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

Fix this in Cyber Protect Home Office Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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