dbcve.org
AgentApplication · Acronis

CVE-2023-45244

HIGH · 7.1 CVSS v3.1 Published 2023-10-06
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 35895, Acronis Cyber Protect 16 (Linux, macOS, 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 · high confidence

Missing authorization in Acronis Cyber Protect Cloud Agent and Cyber Protect 16 allows unauthenticated or unauthorized attackers to access sensitive information and perform data manipulation due to insufficient access control checks in the affected software versions.

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 35895 or later, and Cyber Protect 16 to build 37391 or later, to remediate the missing 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
AgentApplication
Affected:< c23.07

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. Verify Acronis Agent installation
    Locate the Acronis Cyber Protect Agent or Cyber Protect 16 installation on the system. Check for the presence of Acronis service processes or the installation directory.
    Affected if Acronis Agent or Cyber Protect 16 is installed on the system
  2. Identify installed version and build number
    Access the agent's version information through the Acronis management console, registry (if Windows), or by running the agent version command if available in the installation directory.
    Affected if Unable to retrieve version information
  3. Compare against affected version range
    Compare the installed version to the affected threshold. For Acronis Cyber Protect Cloud Agent, check if the build is earlier than 35895. For Cyber Protect 16, check if the build is earlier than 37391. Alternatively, check if the version string indicates a release before c23.07.
    Affected if The installed build is below 35895 (Cloud Agent) or below 37391 (Cyber Protect 16), or the version indicates pre-c23.07
  4. Confirm the agent is actively managing the system
    Verify that the Acronis agent is operational and has active protection policies configured, as the vulnerability affects the authorization checks in the agent's runtime environment.
    Affected if The agent is installed but not active or has no protection policies configured

The system is affected if Acronis Cyber Protect Cloud Agent or Cyber Protect 16 is installed with a build number below 35895 or 37391 respectively (or a version prior to c23.07), and the agent is actively running on the machine.

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 35895 or later, and Cyber Protect 16 to build 37391 or later, to remediate the missing authorization vulnerability.

Recommended fix Moderate confidence

Acronis Cyber Protect Cloud Agent: build 35895 or later; Acronis Cyber Protect 16: build 37391 or later

  1. 1. Identify the currently installed Acronis product (Acronis Cyber Protect Cloud Agent or Acronis Cyber Protect 16) and its current build number
  2. 2. For Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows): Upgrade to build 35895 or later
  3. 3. For Acronis Cyber Protect 16 (Linux, macOS, Windows): Upgrade to build 37391 or later
  4. 4. Verify the upgrade was successful by checking the build number in the agent console or using the command-line tool
  5. 5. Confirm the vulnerability is resolved by reviewing the security advisory at security-advisory.acronis.com

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

Fix this in Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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