dbcve.org
Cyber ProtectApplication · Acronis

CVE-2023-44157

HIGH · 7.8 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 15 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 15 (Windows) before build 35979.

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 15 on Windows where insecure folder permissions allow a low-privileged local user to modify folder contents used by the service, potentially leading to code execution with elevated privileges.

MitigationUpdate Acronis Cyber Protect 15 to build 35979 or later to remediate the insecure folder permission vulnerability.

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 ProtectApplication
Affected:< 15= 15

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 15 installation
    Open Programs and Features in Windows Control Panel or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Acronis*"}' to list installed Acronis products
    Affected if Acronis Cyber Protect 15 appears in the installed programs list
  2. Check installed version number
    Locate the Acronis Cyber Protect 15 entry in Programs and Features and note the Version field, or query the registry key for the exact version number
    Affected if The version is listed as version 15 (any build) or falls below build 35979
  3. Identify Acronis service directories
    Navigate to the Acronis installation directory, typically C:\Program Files\Acronis\ or C:\Program Files (x86)\Acronis\, and identify folders used by the Cyber Protect service
    Affected if Acronis service folders exist in the installation directory
  4. Review folder permissions for weak ACLs
    Right-click on service-related folders, select Properties, then the Security tab. Check the permissions for Users or authenticated users groups. Alternatively, run 'icacls "C:\Program Files\Acronis\*"' in an elevated command prompt to list ACLs
    Affected if Users or low-privileged groups are granted Modify, Write, or Full Control permissions on folders used by the service, allowing them to add, modify, or delete files in those directories

If Acronis Cyber Protect 15 is installed with any version and service folders grant low-privileged users modify or write access, the environment is vulnerable to this privilege escalation flaw.

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

Update Acronis Cyber Protect 15 to build 35979 or later to remediate the insecure folder permission vulnerability.

Recommended fix High confidence

Acronis Cyber Protect 15 build 35979 or later

  1. Identify the currently installed build version of Acronis Cyber Protect 15 on the Windows system
  2. Download Acronis Cyber Protect 15 build 35979 or later from the official Acronis download center or support portal
  3. Run the installer with appropriate administrative privileges
  4. Follow the on-screen prompts to complete the upgrade process
  5. Restart the system if prompted by the installer
  6. Verify the installed build version is 35979 or higher after upgrade

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

Fix this in Cyber Protect 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-2023-44157 — 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-44157 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