CVE-2023-41745
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 excessive collection of system information. The following products are affected: Acronis Agent (Linux, macOS, Windows) before build 30991, Acronis Cyber Protect 15 (Linux, macOS, Windows) before build 35979.
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 confidenceAcronis Agent and Cyber Protect 15 collect excessive system information beyond what is necessary for their legitimate backup/protection functions. This over-collection exposes sensitive system details (potentially including credentials, configuration data, or system identifiers) that could be retrieved by unauthorized actors, leading to information disclosure.
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<= c22.11= 15CVSS 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.
-
Check Acronis Agent versionLocate the Acronis Agent installation and retrieve its version number. This is typically found in the product UI under 'About' or 'Help', or via the command line if available.Affected if The installed version is c22.11 or earlier (any version <= c22.11)
-
Check Acronis Cyber Protect versionLocate the Acronis Cyber Protect 15 installation and retrieve its version/build number. This is typically accessible through the product console under 'Settings' > 'About' or via system information utilities.Affected if The installed version is Cyber Protect 15 (any 15.x release)
-
Confirm product components in useReview the installed Acronis components on the system to determine if the Agent or Cyber Protect functionality is actively running, as the over-collection applies when these components are present.Affected if Acronis Agent (any version) or Acronis Cyber Protect 15 is installed and operational on the system
A system is affected if Acronis Agent version is c22.11 or earlier, or if Acronis Cyber Protect 15 is installed, since these versions contain the excessive system information collection behavior.
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 · scopedUpgrade Acronis Agent to build 30991 or later, and Acronis Cyber Protect 15 to build 35979 or later, as these builds address the excessive information collection.
Acronis Agent build 30991 or later; Acronis Cyber Protect 15 build 35979 or later
- For Acronis Agent (Linux, macOS, Windows): Upgrade to build 30991 or later
- For Acronis Cyber Protect 15 (Linux, macOS, Windows): Upgrade to build 35979 or later
- Verify the upgrade was successful by checking the build number in the product interface or via command line
- Confirm the excessive system information collection has been remediated by reviewing the security advisory at security-advisory.acronis.com
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41745 — 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-41745 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