AgentApplication · Acronis

CVE-2023-45246

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

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 36343, Acronis Cyber Protect 16 (Linux, macOS, Windows) before build 39169.

Technical summary

dbcve analysis · moderate confidence

Missing authorization in Acronis Cyber Protect Cloud Agent and Cyber Protect 16 allows unauthenticated attackers to potentially disclose sensitive information and perform unauthorized manipulation. The vulnerability affects Linux, macOS, and Windows agents before specified build numbers.

MitigationUpdate Acronis Cyber Protect Cloud Agent to build 36343 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

NVD · CPE data

AgentApplication

Affected:< c23.09

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Acronis agent is installed

Identify if Acronis Cyber Protect Cloud Agent or Cyber Protect 16 is installed on the system by checking for the Acronis service or application process

Affected if Acronis agent software is present on the system
Identify installed Acronis agent version

Use system tools or Acronis command-line utilities to retrieve the installed agent build or version number (such as 'agent --version' or checking the agent properties in the management console)

Affected if A version number or build is retrieved from the installed agent
Compare version against affected range

Check if the retrieved version is before c23.09 (such as c23.08, c23.07, or earlier)

Affected if The installed agent version is less than c23.09 (for example, c23.08, c23.07, or any version prior to c23.09)
Verify operating system platform

Confirm the operating system where the agent is installed - the vulnerability affects Linux, macOS, and Windows agents

Affected if The agent is running on Linux, macOS, or Windows and the version is below c23.09

The environment is affected if Acronis Cyber Protect Cloud Agent or Cyber Protect 16 is installed on Linux, macOS, or Windows with a version or build number lower than c23.09.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update Acronis Cyber Protect Cloud Agent to build 36343 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.09 (build 36343); Acronis Cyber Protect 16: build 39169

Identify which Acronis product is installed: Acronis Cyber Protect Cloud Agent or Acronis Cyber Protect 16
For Acronis Cyber Protect Cloud Agent: Upgrade to build 36343 (c23.09) or later for Linux, macOS, or Windows
For Acronis Cyber Protect 16: Upgrade to build 39169 or later for Linux, macOS, or Windows
Verify the upgrade was successful by checking the agent build number
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

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,930

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

security-advisory.acronis.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45246 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2023-45246?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.1 High

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Agent

Remediation

Need this fixed?

Fix this in Agent 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2023-45246 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References