dbcve.org
Cyber ProtectApplication · Acronis

CVE-2024-49388

CRITICAL · 9.1 CVSS v3.1 Published 2024-10-15
Fix available
A fix is available. Upgrade to after 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 manipulation due to improper authorization. The following products are affected: Acronis Cyber Protect 16 (Linux, Windows) before build 38690.

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

Improper authorization vulnerability in Acronis Cyber Protect 16 allows authenticated users to manipulate sensitive information. The critical severity (CVSS 9.1) indicates likely privilege escalation enabling unauthorized modification of protected data.

MitigationUpgrade Acronis Cyber Protect 16 to build 38690 or later on both Linux and Windows platforms to remediate the improper authorization 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= 16

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. Identify Acronis Cyber Protect installation
    On Windows, check Add/Remove Programs or Registry (HKLM\Software\Acronis). On Linux, check installed packages (rpm -qa | grep -i acronis or dpkg -l | grep -i acronis) or look in /opt/acronis directory.
    Affected if Acronis Cyber Protect is not installed or only versions higher than 16 are found (not applicable).
  2. Determine the installed build version
    On Windows, check the About section in the management console or in Registry (HKLM\Software\Acronis\Setup). On Linux, run: /opt/acronis/bin/mgmtsrvr --version or check /var/lib/Acronis/build_info.xml if available.
    Affected if The build version cannot be determined or is not a valid Acronis Cyber Protect build.
  3. Compare build against the fixed version
    Identify the numeric build number from the version output (e.g., build 38690). Compare this build number to 38690.
    Affected if Build number is less than 38690, indicating the vulnerability is not fixed.
  4. Verify product version is affected
    Confirm the product is Cyber Protect 16 or a version <= 15 based on the version string or build metadata.
    Affected if Product version is Cyber Protect 16 or any version 15 and below.

You are affected if Acronis Cyber Protect 16 (or version 15 and below) is installed with a build number lower than 38690, as this combination contains the unpatched improper authorization 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 a release after 15
Interim mitigation

Upgrade Acronis Cyber Protect 16 to build 38690 or later on both Linux and Windows platforms to remediate the improper authorization vulnerability.

Recommended fix High confidence

Acronis Cyber Protect 16 build 38690 or later

  1. 1. Identify the current installed build of Acronis Cyber Protect 16 (check About or system information)
  2. 2. If the current build is before 38690, schedule a maintenance window for the upgrade
  3. 3. Download the latest Acronis Cyber Protect 16 installer from the official Acronis download center or your licensed portal
  4. 4. Run the installer and follow the upgrade procedure, ensuring to back up configuration data first
  5. 5. After upgrade, verify the build number is 38690 or higher
  6. 6. Confirm the vulnerability is remediated by checking the security advisory at security-advisory.acronis.com for the specific patch notes
Caveat Review Acronis release notes for build 38690 to check for any configuration or feature changes that may require adjustments

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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