dbcve.org
AgentApplication · Acronis

CVE-2023-44214

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 Agent (Linux, macOS, Windows) before build 35739.

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

This is an authorization bypass vulnerability in Acronis Agent where missing access control checks allow unauthorized users to access sensitive information. The vulnerability affects Linux, macOS, and Windows agents prior to build 35739.

MitigationUpgrade Acronis Agent to build 35739 or later on all affected platforms to implement proper authorization checks.

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. Verify Acronis Agent is installed
    Check for Acronis Agent processes or service on the system. On Windows, look for 'Acronis Agent' service or 'Acronis' processes in Task Manager or services.msc. On Linux/macOS, check for running processes like 'acronis_agent' or 'agent' using ps aux or similar commands.
    Affected if Acronis Agent software is present on the system
  2. Locate the installed version or build number
    Find the installed Acronis Agent version. On Windows, check the installed programs list in Control Panel or via PowerShell (Get-ItemProperty on the installation directory). On Linux, check /var/lib/Acronis or look for version files in the agent installation directory. On macOS, check /Library/Application Support/Acronis or the .app bundle info.
    Affected if Unable to determine version or version info not found
  3. Compare installed build against the fixed version
    Compare the discovered build number to 35739. The agent is affected if the build number is lower than 35739 (for example, build 35700, 35650, etc.) or if the version string indicates a release earlier than c23.06.
    Affected if Installed build number is less than 35739 or version is earlier than c23.06
  4. Confirm the agent management interface is accessible
    Verify the Acronis Agent management interface or API endpoint is reachable on the network or localhost. This vulnerability allows unauthorized access to sensitive information through the agent interface. Check if port 8443 or similar management ports are open and responding.
    Affected if Management interface is accessible without proper authentication controls

The environment is affected if Acronis Agent is installed with a build number lower than 35739 (or version earlier than c23.06) and the management interface is accessible, allowing unauthorized users to bypass authorization checks.

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 Agent to build 35739 or later on all affected platforms to implement proper authorization checks.

Recommended fix Moderate confidence

Acronis Agent c23.06 (build 35739)

  1. Download Acronis Agent version c23.06 (build 35739) or later from the official Acronis download center or your licensed Acronis portal
  2. Backup the current Acronis Agent configuration and any relevant data
  3. Stop the running Acronis Agent service on the affected system
  4. Install the updated Acronis Agent (c23.06/build 35739+) using the standard installation procedure
  5. After installation, verify the service is running correctly
  6. Confirm the vulnerability is resolved by reviewing system logs and ensuring no unauthorized access attempts remain
Caveat Standard security patch upgrade with minimal risk; ensure configuration backup before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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