dbcve.org
AgentApplication · Acronis

CVE-2022-45457

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) before build 29633, Acronis Cyber Protect 15 (Windows) 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 · moderate confidence

Improper certificate validation in Acronis Agent and Cyber Protect 15 for Windows allows attackers to perform man-in-the-middle attacks, potentially leading to disclosure of sensitive information and manipulation of data in transit due to the application failing to properly validate SSL/TLS certificates.

MitigationUpdate Acronis Agent to build 29633 or later, and Acronis Cyber Protect 15 to build 30984 or later.

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 products
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed software. Look for 'Acronis Agent' or 'Acronis Cyber Protect' entries.
    Affected if Either Acronis Agent or Acronis Cyber Protect 15 is listed in installed programs.
  2. Locate Acronis installation directory
    Common paths include C:\Program Files\Acronis or C:\Program Files (x86)\Acronis. Check for subfolders like 'Agent', 'Cyber Protect', or version-specific folders.
    Affected if Acronis installation directory exists on the system.
  3. Determine installed version and build number
    Right-click the main Acronis executable (often named after the product, such as acronis_agent.exe, cyber_protect.exe, or similar in the bin folder) and select Properties > Details to view File Version and Product Version. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Acronis or HKLM\SOFTWARE\WOW6432Node\Acronis for Version or Build entries.
    Affected if The obtained version or build number is lower than c22.05 for Agent, or the product version is 15 (any build) for Cyber Protect 15.
  4. Verify SSL/TLS functionality is enabled
    Confirm the Acronis Agent or Cyber Protect service is running and that network communication features (backup, restore, remote management) are actively used or configured. Check the product console to see if agent connectivity or cloud backup features are enabled.
    Affected if The Acronis product is installed and its network/backup features are in use or configured, as the certificate validation flaw affects data in transit.

The system is affected if Acronis Agent with version/build lower than c22.05 or Acronis Cyber Protect 15 (any build) is installed and its network communication features are enabled or in use.

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

Update Acronis Agent to build 29633 or later, and Acronis Cyber Protect 15 to build 30984 or later.

Recommended fix Moderate confidence

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

  1. Check the current build version of Acronis Agent (Windows) or Acronis Cyber Protect 15 (Windows)
  2. For Acronis Agent: verify if build number is less than 29633
  3. For Acronis Cyber Protect 15: verify if build number is less than 30984
  4. If the current build is below the fixed version, upgrade to the fixed release that includes build 29633 or higher (Agent) or build 30984 or higher (Cyber Protect 15)
  5. After upgrade, verify the certificate validation issue is resolved

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

Fix this in Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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