dbcve.org
Cyber ProtectApplication · Acronis

CVE-2022-45453

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
TLS/SSL weak cipher suites enabled. The following products are affected: Acronis Cyber Protect 15 (Windows, 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

Acronis Cyber Protect 15 allows TLS/SSL connections using weak cipher suites before build 30984. This could allow a remote attacker to potentially decrypt, tamper with, or forge encrypted traffic by exploiting cryptographic weaknesses in the supported cipher suites.

MitigationUpdate Acronis Cyber Protect 15 to build 30984 or later, which disables weak TLS/SSL cipher suites. Alternatively, if an update is not immediately feasible, manually configure the product to disable weak ciphers (e.g., those using 3DES, RC4, or TLS 1.0/1.1 with weak key lengths).

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 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 Acronis Cyber Protect 15 installation
    Locate the Acronis Cyber Protect 15 installation directory or check installed programs list on the system. Typical paths may include C:\Program Files\Acronis\Cyber Protect or /opt/acronis/cyber-protect on Linux systems.
    Affected if Acronis Cyber Protect 15 is installed on the system
  2. Determine the installed build version
    Find the version or build number of the installed Acronis Cyber Protect 15. This may be visible in the product UI under About or Help, in the Windows Registry, or by running product-specific diagnostic commands.
    Affected if The build number is lower than 30984
  3. Verify weak cipher suite configuration
    Examine the TLS/SSL configuration settings for Acronis Cyber Protect 15. Check for enabled cipher suites including 3DES-based ciphers, RC4-based ciphers, or configurations supporting TLS 1.0/1.1 with weak key lengths. This may be in product configuration files, management console settings, or registry keys.
    Affected if Weak cipher suites such as 3DES, RC4, or TLS 1.0/1.1 with weak key lengths are enabled or permitted
  4. Confirm TLS protocol version settings
    Review TLS protocol settings to determine if TLS 1.0 or TLS 1.1 is enabled in the Acronis Cyber Protect 15 configuration.
    Affected if TLS 1.0 or TLS 1.1 protocols are enabled and not restricted to stronger versions only

A system is affected if Acronis Cyber Protect 15 is installed with a build number lower than 30984 AND weak TLS/SSL cipher suites (3DES, RC4) or legacy TLS protocols (1.0/1.1) are enabled in the configuration.

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 Cyber Protect 15 to build 30984 or later, which disables weak TLS/SSL cipher suites. Alternatively, if an update is not immediately feasible, manually configure the product to disable weak ciphers (e.g., those using 3DES, RC4, or TLS 1.0/1.1 with weak key lengths).

Recommended fix High confidence

Acronis Cyber Protect 15 build 30984 or later

  1. 1. Identify the current build version of Acronis Cyber Protect 15 installed on the system
  2. 2. Download Acronis Cyber Protect 15 build 30984 or later from the official Acronis download center or update server
  3. 3. Apply the update following Acronis standard upgrade procedures for your platform (Windows or Linux)
  4. 4. After upgrade, verify the new build number is 30984 or higher
  5. 5. Confirm TLS/SSL configuration no longer uses weak cipher suites
Caveat Review Acronis release notes for build 30984 for any compatibility or configuration changes before upgrading

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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