dbcve.org
AgentApplication · Acronis

CVE-2023-45241

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 leak through log files. The following products are affected: Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows) before build 35739, 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

Sensitive information is being written to log files in Acronis Cyber Protect Cloud Agent and Acronis Cyber Protect 16. The vulnerability allows potentially sensitive data (credentials, tokens, or personal information) to be exposed in log files that may be accessible to unauthorized users. This affects Linux, macOS, and Windows versions prior to build 35739 (Cloud Agent) and build 37391 (Cyber Protect 16).

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 35739 or later, and Acronis Cyber Protect 16 to build 37391 or later. Review existing log files for any sensitive data exposure and rotate credentials that may have been logged.

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 installed Acronis product
    Check installed programs on Windows (Programs and Features), or list installed packages on Linux (dpkg -l | grep -i acronis or rpm -qa | grep -i acronis), or check Applications folder on macOS. Determine if you have Acronis Cyber Protect Cloud Agent or Acronis Cyber Protect 16 installed.
    Affected if Neither Acronis product is installed, then not affected.
  2. Check build version on Windows
    Open Windows Registry and navigate to HKLM\SOFTWARE\Acronis\MMS\ or check the installed program properties in Control Panel to find the build number. Look for a version or build field.
    Affected if The displayed build number is less than 35739 for Cloud Agent, or less than 37391 for Cyber Protect 16.
  3. Check build version on Linux
    Run command: rpm -qa | grep -i acronis or dpkg -l | grep -i acronis to list installed Acronis packages, then run rpm -qi <package_name> or dpkg -s <package_name> to see version and build details.
    Affected if The displayed build number is less than 35739 for Cloud Agent, or less than 37391 for Cyber Protect 16.
  4. Check build version on macOS
    Open Terminal and run: defaults read /Applications/Acronis\ Cyber\ Protect\ *.app/Contents/Info CFBundleVersion or check the application bundle info.plist for version and build numbers.
    Affected if The displayed build number is less than 35739 for Cloud Agent, or less than 37391 for Cyber Protect 16.

You are affected if Acronis Cyber Protect Cloud Agent with build below 35739 or Acronis Cyber Protect 16 with build below 37391 is installed on Linux, macOS, or Windows.

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 35739 or later, and Acronis Cyber Protect 16 to build 37391 or later. Review existing log files for any sensitive data exposure and rotate credentials that may have been logged.

Recommended fix High confidence

Acronis Cyber Protect Cloud Agent c23.06 (build 35739) or Acronis Cyber Protect 16 c23.06 (build 37391)

  1. Identify the currently installed Acronis Cyber Protect Cloud Agent or Acronis Cyber Protect 16 version using the product's built-in version check or system information
  2. For Acronis Cyber Protect Cloud Agent: Upgrade to version c23.06 (build 35739) or later for Linux, macOS, and Windows
  3. For Acronis Cyber Protect 16: Upgrade to version c23.06 (build 37391) or later for Linux, macOS, and Windows
  4. Verify the upgrade was successful by checking the product version matches or exceeds the fixed builds
  5. Review log files after upgrade to confirm sensitive information is no longer being written to logs

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-45241 — 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-45241 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