dbcve.org
AgentApplication · Acronis

CVE-2023-45240

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

Acronis Agent before build 35739 contains a missing authorization vulnerability that allows unauthorized access to sensitive information. An attacker could exploit this to disclose sensitive data due to the lack of proper authorization checks in the affected component.

MitigationUpgrade Acronis Agent to build 35739 or later to remediate the missing authorization vulnerability.

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 installation
    Check the system for Acronis Agent software - look in installed programs list, services panel, or common installation directories for evidence of Acronis Agent.
    Affected if Acronis Agent is present on the system
  2. Identify Acronis Agent build version
    Locate and retrieve the installed build version of Acronis Agent - check the agent's About section, installed software metadata, or version information in the Acronis management interface.
    Affected if The build version cannot be determined or is below c23.06
  3. Compare build against affected threshold
    Compare the installed build number to the affected range: any version below build 35739 (or c23.06) is within the vulnerable range.
    Affected if Installed build is 35738 or lower, or the version string indicates c23.05 or earlier
  4. Check if affected component is configured
    Determine whether the affected component that lacks authorization checks is enabled or accessible on the system - this may be a specific agent service, API endpoint, or management interface component.
    Affected if The vulnerable component is exposed or enabled

The system is affected if Acronis Agent is installed with a build version below 35739 (c23.06) and the vulnerable component is accessible.

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 to remediate the missing authorization vulnerability.

Recommended fix High confidence

Acronis Agent c23.06 (build 35739 or later)

  1. Identify the current Acronis Agent version installed on each affected system (Linux, macOS, or Windows)
  2. Access the official Acronis download center or your licensed Acronis customer portal
  3. Download Acronis Agent version c23.06 or later (build 35739+) for your respective platform
  4. Review Acronis upgrade documentation for your specific platform before proceeding
  5. Create a backup of your current Acronis configuration and any critical data
  6. Upgrade the Acronis Agent on each affected system using the standard upgrade procedure for your platform
  7. After upgrade, verify the installed build number is 35739 or higher
  8. Confirm that the authorization controls are functioning properly and sensitive operations require proper authentication
Caveat Review Acronis release notes for c23.06 to check for any behavior changes or deprecated features that may affect your backup workflows

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

Fix this in Agent Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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