dbcve.org
Cyber BackupApplication · Acronis

CVE-2022-30995

HIGH · 7.5 CVSS v3.1 Published 2023-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 improper authentication. The following products are affected: Acronis Cyber Protect 15 (Windows, Linux) before build 29486, Acronis Cyber Backup 12.5 (Windows, Linux) before build 16545.

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

Sensitive information disclosure vulnerability in Acronis Cyber Protect 15 and Cyber Backup 12.5 caused by improper authentication. Attackers can potentially access sensitive data due to insufficient authentication controls. Fixed in build 29486 for Cyber Protect 15 and build 16545 for Cyber Backup 12.5.

MitigationUpgrade to Acronis Cyber Protect 15 build 29486 or later, or Cyber Backup 12.5 build 16545 or later to address the improper authentication 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
Cyber BackupApplication
Affected:= 12.5
Cyber ProtectApplication
Affected:= 15

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed Acronis product
    Locate Acronis installation directory or check installed programs list for 'Acronis Cyber Protect 15' or 'Acronis Cyber Backup 12.5'
    Affected if Either product version 15 or 12.5 is installed
  2. Check Cyber Protect 15 build number
    Open Acronis Cyber Protect management console, navigate to Help > About, or run: C:\Program Files\Acronis\Agent\bin\agent_protected_version.exe (path may vary by installation)
    Affected if Build number is present but lower than 29486
  3. Check Cyber Backup 12.5 build number
    Open Acronis Cyber Backup management console, navigate to Help > About, or check Windows Programs and Features for build information
    Affected if Build number is present but lower than 16545
  4. Verify management interface exposure
    Check if Acronis management ports (default TCP 9877, 9878, or custom ports) are accessible from untrusted networks
    Affected if Management console is reachable from outside trusted network without additional authentication layers

User is affected if Acronis Cyber Protect 15 with build below 29486 or Cyber Backup 12.5 with build below 16545 is installed and the management interface is network-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 to Acronis Cyber Protect 15 build 29486 or later, or Cyber Backup 12.5 build 16545 or later to address the improper authentication vulnerability.

Recommended fix High confidence

Acronis Cyber Protect 15 build 29486 or later; Acronis Cyber Backup 12.5 build 16545 or later

  1. 1. Identify the current installed version of Acronis Cyber Protect 15 or Cyber Backup 12.5 by accessing the management console or checking the installed software information
  2. 2. Compare your current build number against the fixed releases: Cyber Protect 15 requires build 29486 or later; Cyber Backup 12.5 requires build 16545 or later
  3. 3. If your current build is below the fixed version, download the updated build from the official Acronis download center or your licensed Acronis account
  4. 4. Follow Acronis standard upgrade procedures: ensure backup of current configuration, stop the Acronis services if prompted, run the installer for the new build
  5. 5. After installation completes, verify the new build number matches or exceeds the fixed versions (29486 for Cyber Protect 15, 16545 for Cyber Backup 12.5)
  6. 6. Confirm the vulnerability is resolved by reviewing the security advisory at security-advisory.acronis.com
Caveat Review Acronis release notes for your specific build for any configuration or feature changes; standard upgrade precautions apply (backup configuration before upgrading)

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

Fix this in Cyber Backup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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