dbcve.org
Cyber Protect Home OfficeApplication · Acronis

CVE-2023-5042

HIGH · 7.5 CVSS v3.1 Published 2023-09-20
Fix available
A fix is available. Upgrade to 40713 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 40713, Acronis True Image OEM (Windows) before build 42575.

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

Insecure folder permissions in Acronis Cyber Protect Home Office and Acronis True Image OEM allow local unauthorized users to access sensitive files stored on the system due to overly permissive access control lists on application directories.

MitigationUpgrade to Acronis Cyber Protect Home Office build 40713 or Acronis True Image OEM build 42575 or later to obtain corrected folder permissions that restrict access to sensitive data.

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

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
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 checks

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

  1. Identify installed Acronis product
    Check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Acronis Cyber Protect Home Office' or 'Acronis True Image OEM', or inspect Program Files directories for Acronis installation folders
    Affected if Either Acronis Cyber Protect Home Office or Acronis True Image OEM is found installed on the system
  2. Determine Acronis Cyber Protect Home Office build version
    Locate the installed product in Registry under HKLM\SOFTWARE\Acronis\Cyber Protect Home Office\ or check the application's About/Version information, then record the build number
    Affected if The build version is less than 40713
  3. Determine Acronis True Image OEM build version
    Locate the installed product in Registry under HKLM\SOFTWARE\Acronis\True Image OEM\ or check the application's About/Version information, then record the build number
    Affected if The build version is less than 42575 (or the specific affected version range for the OEM variant)
  4. Inspect Acronis application folder permissions
    Right-click the Acronis installation directory (typically in Program Files or Program Files (x86)), select Properties, then go to the Security tab. Check if groups such as Everyone, Users, orAuthenticated Users have Full Control or Modify permissions
    Affected if Broad user groups like Everyone or Users are granted Full Control or Modify access to the application directory containing sensitive data

A system is affected if either Acronis Cyber Protect Home Office build is below 40713 or Acronis True Image OEM build is below 42575, AND the application folder permissions grant overly broad access to standard users or Everyone.

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

Upgrade to Acronis Cyber Protect Home Office build 40713 or Acronis True Image OEM build 42575 or later to obtain corrected folder permissions that restrict access to sensitive data.

Recommended fix Moderate confidence

Acronis Cyber Protect Home Office build 40713 or later; Acronis True Image OEM build 42575 or later

  1. Identify the installed Acronis product (Cyber Protect Home Office or True Image OEM) by checking the application version in the Help/About section
  2. Download the updated version from the official Acronis website or through the product's built-in update mechanism
  3. Install the update to build 40713 or later for Cyber Protect Home Office, or build 42575 or later for True Image OEM
  4. Verify the installation was successful by confirming the new build number in the application's About section

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-2023-5042 — 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-2023-5042 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