dbcve.org
Cyber ProtectApplication · Acronis

CVE-2023-44159

HIGH · 7.5 CVSS v3.1 Published 2023-09-27
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 due to cleartext storage of sensitive information. The following products are affected: Acronis Cyber Protect 15 (Linux, Windows) before build 35979.

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 (Linux and Windows) before build 35979 due to cleartext storage of sensitive information. Attackers with access to stored data can retrieve sensitive information that should have been encrypted.

MitigationUpgrade to Acronis Cyber Protect 15 build 35979 or later. If immediate upgrade is not feasible, conduct a data audit to identify and encrypt any sensitive data currently stored in cleartext, and implement compensating controls to restrict access to storage locations.

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. Check installed Acronis Cyber Protect 15 version and build number
    Locate the Acronis Cyber Protect 15 installation and retrieve its version information. On Windows, check the product version in Programs and Features or the about section of the management console. On Linux, check using the product command-line tools or rpm/dpkg package information.
    Affected if The installed build number is lower than 35979, or the version is any release of version 15 prior to the build that includes the fix.
  2. Identify storage locations used by Acronis Cyber Protect 15
    Examine the Acronis Cyber Protect 15 data directories and configuration to determine where backup data, configuration files, and sensitive information are stored. Common locations include the installation directory, data storage paths, and configuration folders.
    Affected if Sensitive data storage directories exist and the product version is in the affected range.
  3. Inspect stored data for cleartext sensitive information
    Examine files in the identified storage locations for unencrypted sensitive information such as credentials, encryption keys, or personal data that should have been protected. Use file inspection tools to examine the content of data files stored by the product.
    Affected if Any sensitive data is found stored in cleartext (unencrypted) format in the product's storage locations.
  4. Verify access controls on data storage locations
    Review file system permissions and access controls on the directories where Acronis Cyber Protect 15 stores data. Check which users and processes have read access to these locations.
    Affected if Storage locations containing sensitive data have overly permissive access controls, allowing unauthorized users or processes to read stored data.

A system is affected if Acronis Cyber Protect 15 is installed with a build number lower than 35979 and sensitive data is stored in cleartext in accessible storage locations.

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 to Acronis Cyber Protect 15 build 35979 or later. If immediate upgrade is not feasible, conduct a data audit to identify and encrypt any sensitive data currently stored in cleartext, and implement compensating controls to restrict access to storage locations.

Recommended fix High confidence

Acronis Cyber Protect 15 build 35979 or later

  1. Backup your current Acronis Cyber Protect 15 installation, configuration, and all critical data
  2. Download Acronis Cyber Protect 15 build 35979 or later from the official Acronis download portal or licensing portal
  3. Review the official Acronis upgrade documentation for your specific platform (Linux or Windows)
  4. Stop the Acronis Cyber Protect services before upgrading
  5. Install the updated build following Acronis standard upgrade procedures for your platform
  6. Restart the Acronis Cyber Protect services after installation
  7. Verify the installation was successful by checking the build version in the product UI or via command line
  8. Confirm the vulnerability is remediated by verifying sensitive information is no longer stored in cleartext

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

Fix this in Cyber Protect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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