dbcve.org
Cyber ProtectApplication · Acronis

CVE-2023-44206

CRITICAL · 9.1 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 15 or later.
See remediation →
100/100
Remediation priority · Urgent
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 and manipulation due to improper authorization. The following products are affected: Acronis Cyber Protect 15 (Linux, 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 · high confidence

Improper authorization vulnerability in Acronis Cyber Protect 15 allows unauthenticated or unauthorized attackers to bypass access controls, leading to sensitive information disclosure and potential data manipulation. The flaw exists in both Linux and Windows versions before build 35979.

MitigationUpdate Acronis Cyber Protect 15 to build 35979 or later to remediate the authorization flaw. Prior to production deployment, validate the update in a non-production environment to ensure compatibility with existing backup and protection workflows.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Verify Acronis Cyber Protect 15 is installed
    On Windows, check Services for 'Acronis Cyber Protect' service or look in Program Files for Acronis folder. On Linux, check for installed packages via rpm -qa | grep -i acronis or dpkg -l | grep -i acronis.
    Affected if The product Acronis Cyber Protect 15 is found installed on the system.
  2. Locate the installed build version
    On Windows, open the Acronis Cyber Protect console and navigate to Help > About to view the build number. Alternatively, check the registry key HKLM\SOFTWARE\Acronis\Global\Install or look in C:\ProgramData\Acronis\Install\manifest.json for the build field. On Linux, run /usr/lib/Acronis/backup_utils/Version or check /etc/Acronis/version.info.
    Affected if A build number is retrieved from the installation.
  3. Compare build number against affected range
    Take the build number found in the previous step and compare it numerically to 35979. If the build is less than 35979 (for example 35900, 35600, 34000), the system is within the vulnerable range.
    Affected if The installed build number is lower than 35979 (for example, 35978, 35850, or 35700).
  4. Assess exposure of management interface
    Determine if the Acronis management port (typically 9876 or 443) is accessible from untrusted networks. Use 'netstat -an | grep -E "(9876|443)"' on Linux or 'netstat -an | findstr "9876"' on Windows to check listening status. Verify firewall rules allow external access to these ports.
    Affected if The Acronis management service is listening and reachable from network segments that include untrusted or internet-facing IP addresses.

If Acronis Cyber Protect 15 is installed with a build number below 35979 and its management interface is network-accessible, the environment is affected by this authorization bypass vulnerability.

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 authorization flaw. Prior to production deployment, validate the update in a non-production environment to ensure compatibility with existing backup and protection workflows.

Recommended fix Moderate confidence

Acronis Cyber Protect 15 build 35979 or later

  1. 1. Identify the current Acronis Cyber Protect 15 build version by accessing the management console or running the appropriate version check command
  2. 2. Navigate to the official Acronis download center or licensing portal at https://www.acronis.com/ or contact Acronis support for the updated build 35979 or later
  3. 3. Download the Acronis Cyber Protect 15 installer for your platform (Linux or Windows)
  4. 4. Create a complete backup of the current Acronis configuration and any critical data before proceeding
  5. 5. Test the upgrade in a non-production environment if possible to verify compatibility
  6. 6. Apply the upgrade following Acronis installation documentation - typically running the installer with appropriate administrative privileges
  7. 7. After upgrade completion, verify the build number has updated to 35979 or higher and confirm the management console is accessible

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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