CVE-2023-45243
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 · uneditedSensitive 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 · moderate confidenceAcronis Cyber Protect Cloud Agent and Cyber Protect 17 contain a missing authorization vulnerability that allows unauthorized users to access sensitive information. The flaw exists in all supported platforms (Linux, macOS, Windows) in versions prior to build 35739 (Cloud Agent) and build 41186 (Cyber Protect 17).
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< c23.06CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Acronis Agent installationCheck if Acronis Cyber Protect Agent is installed on the system. On Windows, look for the Acronis service or check Program Files. On Linux, run 'rpm -qa | grep -i acronis' or 'dpkg -l | grep -i acronis'. On macOS, check /Applications or run 'pkgutil --pkgs | grep -i acronis'.Affected if Acronis Agent is installed and running on the system
-
Identify Acronis Agent build version on WindowsOpen Windows Registry and navigate to HKLM\SOFTWARE\Acronis\Agent\Settings (or HKLM\SOFTWARE\WOW6432Node\Acronis\Agent\Settings). Look for values such as 'Build' or 'AgentVersion' that display the numeric build number.Affected if The build number is less than 35739 for Cloud Agent or less than 41186 for Cyber Protect 17
-
Identify Acronis Agent build version on LinuxRun the command '/opt/acronis/bin/MMAgent -v' or check the version file if available in the installation directory (commonly /usr/lib/acronis or /opt/acronis). The output typically displays the build number.Affected if The build number is less than 35739 for Cloud Agent or less than 41186 for Cyber Protect 17
-
Identify Acronis Agent build version on macOSRun the command '/Applications/Acronis Cyber Protect.app/Contents/MacOS/MMAgent -v' or right-click the Acronis Cyber Protect application in /Applications, select 'Get Info', and check the version information.Affected if The build number is less than 35739 for Cloud Agent or less than 41186 for Cyber Protect 17
-
Confirm product type and version rangeCross-reference the identified build number with the product type (Cloud Agent vs Cyber Protect 17). Cloud Agent versions prior to c23.06 (build 35739) and Cyber Protect 17 versions prior to build 41186 are affected.Affected if The installed build number falls below 35739 for Cloud Agent/c23.06 or below 41186 for Cyber Protect 17
The environment is affected if Acronis Cyber Protect Agent or Cyber Protect 17 is installed with a build number below 35739 (Cloud Agent/c23.06) or below 41186 (Cyber Protect 17), as these versions lack the required authorization controls.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor-supplied updates to upgrade to build 35739 or later for Cyber Protect Cloud Agent, and build 41186 or later for Cyber Protect 17, then verify the authorization controls are functioning correctly.
Acronis Cyber Protect Cloud Agent build 35739+; Acronis Cyber Protect 17 build 41186+
- Identify the currently installed Acronis Cyber Protect Agent version by checking the build number in the agent management console or via command line
- For Acronis Cyber Protect Cloud Agent: Upgrade to build 35739 or later for Linux, macOS, and Windows agents
- For Acronis Cyber Protect 17: Upgrade to build 41186 or later for Linux, macOS, and Windows agents
- After upgrade, verify the agent is running the corrected build and confirm the authorization vulnerability is resolved
- Test that normal backup and protection functionality continues to work as expected post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45243 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-45243 in production — separate from our analysis above.
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.
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.
- 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