dbcve.org
AgentApplication · Acronis

CVE-2022-45458

HIGH · 7.5 CVSS v3.1 Published 2023-05-18
Fix available
A fix is available. Upgrade to 15 or later.
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 and manipulation due to improper certification validation. The following products are affected: Acronis Agent (Windows, macOS, Linux) before build 29633, Acronis Cyber Protect 15 (Windows, macOS, Linux) before build 30984.

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 confidence

Improper SSL/TLS certificate validation in Acronis Agent and Cyber Protect 15 allows man-in-the-middle attackers to intercept sensitive data and manipulate communications by presenting invalid certificates. The vulnerability stems from the application failing to properly verify the authenticity of SSL/TLS certificates from remote connections.

MitigationUpgrade Acronis Agent to build 29633 or later, and Acronis Cyber Protect 15 to build 30984 or later. Verify that proper certificate chain validation is enforced in the updated versions.

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:< c22.05
Cyber ProtectApplication
Affected:< 15= 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
    On Windows, open Programs and Features or check Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Acronis entries. On Linux, run 'rpm -qa | grep -i acronis' or 'dpkg -l | grep -i acronis'. Check the product name listed (Agent or Cyber Protect 15).
    Affected if Acronis Agent or Acronis Cyber Protect 15 is found installed on the system
  2. Determine Acronis Agent version
    Open Acronis Cyber Protect console or run 'C:\Program Files\Acronis\Agent\bin\agent_version.exe' (Windows) or '/usr/lib/Acronis/agent/bin/agent --version' (Linux). Note the full build number displayed.
    Affected if The version shows build number lower than 29633 (for example, c22.04 or earlier)
  3. Determine Acronis Cyber Protect 15 version
    Open Cyber Protect console, go to Help > About, or run the management tool to view the installed build number. On Windows, also check HKLM\SOFTWARE\Acronis\MMS\Install\Build in registry.
    Affected if The build number is any version of Cyber Protect 15 (all builds are affected)
  4. Compare against affected version ranges
    For Acronis Agent: verify the installed build is below c22.05 (build 29633). For Cyber Protect 15: confirm the installed build is below 30984 or exactly 15.
    Affected if Agent version is less than c22.05, OR Cyber Protect 15 is any version including version 15

You are affected if Acronis Agent with build below 29633 or any version of Cyber Protect 15 is installed, due to improper SSL/TLS certificate validation in these versions.

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
Upgrade available Upgrade to 15 or later
Fixed in 15
Interim mitigation

Upgrade Acronis Agent to build 29633 or later, and Acronis Cyber Protect 15 to build 30984 or later. Verify that proper certificate chain validation is enforced in the updated versions.

Recommended fix High confidence

Acronis Agent c22.05 (build 29633+) or Acronis Cyber Protect 15 build 30984+

  1. 1. Identify the currently installed Acronis product (Agent or Cyber Protect 15) and verify the current build number
  2. 2. Navigate to the official Acronis download center or access the Acronis Cyber Protect console
  3. 3. Download the fixed version: Acronis Agent c22.05 (build 29633 or later) or Acronis Cyber Protect 15 build 30984 or later
  4. 4. Review the Acronis upgrade documentation and release notes for your specific platform (Windows, macOS, or Linux)
  5. 5. Follow the standard Acronis upgrade procedure: stop the Acronis services, install the new build, and restart services
  6. 6. Verify the upgrade was successful by checking the build number in the product interface or via command line
  7. 7. Confirm that certificate validation is now properly enforced
Caveat Review Acronis release notes for version-specific changes and ensure compatibility with your current backup infrastructure before upgrading

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

Fix this in Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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