dbcve.org
AgentApplication · Acronis

CVE-2023-45242

MEDIUM · 5.5 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 →
57/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 due to missing authorization. The following products are affected: Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows) before build 35739, Acronis Cyber Protect 17 (Linux, macOS, Windows) before build 41186.

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

This vulnerability allows unauthorized access to sensitive information due to missing authorization checks in Acronis Cyber Protect Cloud Agent and Acronis Cyber Protect 17. An attacker could potentially access sensitive data without proper authentication or authorization on Linux, macOS, or Windows systems running vulnerable versions of the software.

MitigationUpdate Acronis Cyber Protect Cloud Agent to build 35739 or later, and Acronis Cyber Protect 17 to build 41186 or later, using Acronis management console or standard patching procedures.

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

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if Acronis agent is installed
    On Windows, check Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName' in PowerShell. On Linux, check for installed packages using 'dpkg -l | grep acronis' or 'rpm -qa | grep acronis'. On macOS, check /Applications or run 'ls /Library/Application Support/Acronis'.
    Affected if Acronis Cyber Protect Cloud Agent or Acronis Cyber Protect 17 is installed on the system
  2. Determine the installed Acronis version and build number
    On Windows, open Acronis Cyber Protection agent UI and navigate to Help > About, or check the registry key 'HKLM\SOFTWARE\Acronis\MMS\Setup\ProductVersion' if available. On Linux, run '/usr/lib/acronis/agent version' or check rpm/dpkg package details with 'rpm -qi acronis-agent' or 'dpkg -s acronis-agent'. On macOS, right-click the Acronis app in Applications and select Get Info, or run 'productutil -p' on the .pkg.
    Affected if The version cannot be determined or is lower than c23.06
  3. Compare installed version against affected threshold
    For Acronis Cyber Protect Cloud Agent: verify if the build number is lower than 35739. For Acronis Cyber Protect 17: verify if the build number is lower than 41186. Note that version 'c23.06' corresponds to build 35739 for Cloud Agent. The general threshold for both products is version c23.06 or earlier.
    Affected if The installed build number is below 35739 for Cloud Agent, or below 41186 for Cyber Protect 17, or the version string is c23.06 or earlier
  4. Confirm the operating system is Linux, macOS, or Windows
    Run 'systeminfo' on Windows, 'uname -a' on Linux, or 'sw_vers' on macOS to identify the OS. This CVE affects all three platforms.
    Affected if The system is running Linux, macOS, or Windows with a vulnerable Acronis agent version

The environment is affected if Acronis Cyber Protect Cloud Agent or Cyber Protect 17 is installed with a version earlier than c23.06 (build 35739 for Cloud Agent) or earlier than build 41186 for Cyber Protect 17, on Linux, macOS, or Windows systems.

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

Update Acronis Cyber Protect Cloud Agent to build 35739 or later, and Acronis Cyber Protect 17 to build 41186 or later, using Acronis management console or standard patching procedures.

Recommended fix High confidence

Acronis Cyber Protect Cloud Agent build 35739+ or Acronis Cyber Protect 17 build 41186+

  1. 1. Identify the currently installed Acronis Cyber Protect Agent version on the affected system
  2. 2. For Acronis Cyber Protect Cloud Agent: upgrade to build 35739 or later
  3. 3. For Acronis Cyber Protect 17: upgrade to build 41186 or later
  4. 4. Verify the upgrade was successful by checking the new build number
  5. 5. Test that the Agent is functioning properly and communicating with the management server

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 / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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-2023-45242 — 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-45242 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