dbcve.org
AgentApplication · Acronis

CVE-2023-44213

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 excessive collection of system information. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows) before build 35739, Acronis Cyber Protect 16 (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 · moderate confidence

Acronis Cyber Protect agents for Windows collect excessive system information beyond what is necessary for their protective functions, leading to sensitive information disclosure. This could expose system details, configuration data, or other telemetry that should not be collected or exposed.

MitigationUpdate Acronis Cyber Protect Cloud Agent to build 35739 or later, and Acronis Cyber Protect 16 to build 37391 or later. Review system information collection policies post-update to confirm only necessary data is gathered.

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 Cyber Protect Agent is installed
    Open Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Acronis*"}' in PowerShell to list installed Acronis products
    Affected if No Acronis product is listed means not applicable; if Acronis Cyber Protect or Acronis Agent appears in the list, proceed to version check
  2. Determine the installed Acronis Agent version
    Check the agent service version by running 'Get-Service -Name "Acronis*"' to find the service, then right-click the Acronis agent executable in Program Files\Acronis\Agent\bin\ (such as acronis_agent.exe or management_agent.exe), select Properties, and view the File Version on the Details tab
    Affected if Unable to locate the agent executable or service indicates the product may not be present in the expected form
  3. Compare installed version against affected range
    If you obtained a version number, compare the build number to the threshold: affected if version is earlier than build c23.06 (or build number below 35739 for Cyber Protect Cloud, below 37391 for Cyber Protect 16). The exact version format may appear as a build number or a product version string.
    Affected if The installed agent version is earlier than c23.06 build - verify whether the version string indicates a pre-c23.06 release

Your environment is affected if Acronis Cyber Protect Agent for Windows is installed with a version earlier than c23.06 (or build numbers below 35739/37391), as that version collects excessive system telemetry beyond what is necessary for protection.

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 16 to build 37391 or later. Review system information collection policies post-update to confirm only necessary data is gathered.

Recommended fix Moderate confidence

Acronis Cyber Protect Cloud Agent (Windows) build 35739 or later; Acronis Cyber Protect 16 (Windows) build 37391 or later

  1. Check current Agent build version by reviewing installed software properties or Acronis management console
  2. Download or obtain Acronis Cyber Protect Cloud Agent version c23.06 or later (containing build 35739) from official Acronis sources
  3. Download or obtain Acronis Cyber Protect 16 with build 37391 or later from official Acronis sources
  4. Apply the upgrade through Acronis management console or by reinstalling the agent with the fixed build
  5. Verify the build number post-upgrade matches 35739 (Cloud Agent) or 37391 (Cyber Protect 16)

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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