dbcve.org
AgentApplication · Acronis

CVE-2023-45247

HIGH · 7.1 CVSS v3.1 Published 2023-10-09
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 36497, Acronis Cyber Protect 16 (Linux, macOS, Windows) before build 39169.

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 in Acronis Cyber Protect products allows unauthenticated attackers to access sensitive information and perform unauthorized manipulations. The vulnerability exists in both the Cloud Agent and Cyber Protect 16 across Linux, macOS, and Windows platforms.

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 36497 or later, and Acronis Cyber Protect 16 to build 39169 or later to remediate the authorization bypass.

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.10

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 installed Acronis product
    Locate Acronis Cyber Protect Agent or Acronis Cyber Protect 16 installation on the system
    Affected if The system has Acronis Cyber Protect Cloud Agent or Cyber Protect 16 installed
  2. Determine installed version
    Use the system's software inventory or Acronis management tool to retrieve the exact build version of the Acronis Agent
    Affected if The retrieved build version is lower than c23.10 (for Cloud Agent) or the installed version is any version of Cyber Protect 16 prior to build 39169
  3. Confirm operating system platform
    Check whether the system runs Linux, macOS, or Windows
    Affected if The affected OS platforms are Linux, macOS, or Windows respectively, and the version check in step 2 indicates a vulnerable version
  4. Verify the authorization module is active
    Confirm that the Acronis Agent service or daemon is running and the Cloud/cyber protection features are enabled
    Affected if The agent is active and the vulnerable authorization component is present in the installed version

A system is affected if it runs Acronis Cyber Protect Cloud Agent with a version below c23.10 or Cyber Protect 16 below build 39169 on Linux, macOS, or Windows, and the agent is installed and operational.

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 36497 or later, and Acronis Cyber Protect 16 to build 39169 or later to remediate the authorization bypass.

Recommended fix High confidence

Acronis Cyber Protect Cloud Agent c23.10 (build 36497+) or Acronis Cyber Protect 16 (build 39169+)

  1. 1. Identify the current Acronis Agent version installed on affected Linux, macOS, or Windows systems using the agent's version information or management console
  2. 2. For Acronis Cyber Protect Cloud Agent: Upgrade to version c23.10 or later, which corresponds to build 36497 or higher
  3. 3. For Acronis Cyber Protect 16: Upgrade to build 39169 or later
  4. 4. Verify the upgrade was successful by checking the agent build number in the Acronis management console or via the agent's about/version information
  5. 5. Confirm that the missing authorization vulnerability is remediated by verifying the agent is running the fixed build

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

Fix this in Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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