dbcve.org
AgentApplication · Acronis

CVE-2023-44211

HIGH · 7.1 CVSS v3.1 Published 2023-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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 disclosure and manipulation due to missing authorization. The following products are affected: Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows) before build 31637, Acronis Cyber Protect 16 (Linux, Windows) before build 37391.

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

Missing authorization checks in Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows before build 31637) and Cyber Protect 16 (Linux, Windows before build 37391) allow unauthenticated or unauthorized users to access sensitive information and potentially manipulate data. The vulnerability stems from endpoints or functions lacking proper access control validation.

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 31637 or later, and Acronis Cyber Protect 16 to build 37391 or later. Apply network segmentation and monitor for unauthorized access attempts until patches are deployed.

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
AgentApplication
Affected:< c23.02

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
None

CVSS:3.1/AV:L/AC:L/PR:L/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 Agent installation
    Locate the installed Acronis Cyber Protect agent on the system. On Windows, check Programs and Features or the installation directory. On Linux/macOS, check common installation paths or use package management tools (dpkg/rpm for Linux, ls /Applications on macOS).
    Affected if Acronis Cyber Protect Cloud Agent or Cyber Protect 16 is installed and the version is below the fixed builds.
  2. Determine the installed build number
    Run the agent's version check command. On Windows, this may be via the agent UI, registry, or command line (such as the acronis_agent command or checking the Windows Services description). On Linux/macOS, check the installed package version or run 'acronis_agent --version' if available. Alternatively, inspect the agent service information through the management console.
    Affected if The build number is below 31637 for Cloud Agent or below 37391 for Cyber Protect 16.
  3. Confirm the product version matches affected ranges
    Compare the identified build number to the affected version range. The vulnerability affects versions before c23.02 (which corresponds to build 31637 for Cloud Agent and build 37391 for Cyber Protect 16).
    Affected if The installed build number is lower than 31637 (Cloud Agent) or 37391 (Cyber Protect 16), or the version string indicates c23.02 or earlier.
  4. Verify network exposure of management interface
    Review network configuration to determine if the Acronis management port/service is accessible from unauthorized networks. Check firewall rules and network segmentation around the Acronis agent ports.
    Affected if The management interface is exposed to untrusted networks without proper access controls, increasing exploitability.
  5. Review access logs for anomalies
    Examine Acronis agent logs and system audit logs for unauthorized API calls or access attempts to sensitive endpoints that should require authorization. Look for unusual access patterns from unexpected sources.
    Affected if Logs show access from unauthorized users or unexpected sources to sensitive agent functions or data.

You are affected if the installed Acronis Cyber Protect Cloud Agent build is below 31637 or Cyber Protect 16 build is below 37391, and the agent is accessible to unauthenticated users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Acronis Cyber Protect Cloud Agent to build 31637 or later, and Acronis Cyber Protect 16 to build 37391 or later. Apply network segmentation and monitor for unauthorized access attempts until patches are deployed.

Recommended fix High confidence

Acronis Cyber Protect Cloud Agent c23.02 (build 31637+) or Acronis Cyber Protect 16 build 37391+

  1. 1. Identify the currently installed Acronis Cyber Protect Agent version by checking the build number in the agent UI or via command line (e.g., acronis_agent --version)
  2. 2. Navigate to the official Acronis download center or access your Acronis management console to obtain the updated agent installer
  3. 3. Download Acronis Cyber Protect Cloud Agent version c23.02 or later (build 31637+) for Linux/macOS/Windows, or Acronis Cyber Protect 16 version with build 37391+
  4. 4. Stop all Acronis services running on the affected system before applying the update
  5. 5. Install the updated agent using the downloaded installer, following the standard upgrade procedure
  6. 6. After installation completes, verify that the agent is running the fixed build version (31637 or higher for Cloud Agent; 37391 or higher for Cyber Protect 16)
  7. 7. Confirm the CVE-2023-44211 vulnerability is remediated by verifying authorization checks are now properly enforced

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

Fix this in Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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