dbcve.org
Cyber ProtectApplication · Acronis

CVE-2023-44158

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 insufficient token field masking. 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 · high confidence

Sensitive information disclosure vulnerability in Acronis Cyber Protect 15 where token fields are insufficiently masked, potentially exposing authentication tokens or session credentials to unauthorized users. The insufficient masking allows sensitive authentication data to be visible in the UI or logs.

MitigationUpgrade Acronis Cyber Protect 15 to build 35979 or later to remediate the token field masking issue.

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. Confirm Acronis Cyber Protect 15 is installed
    Check the installed version of Acronis Cyber Protect through the system control panel, installed programs list, or by running 'msinfo32' and looking for Acronis Cyber Protect 15 in the installed software. Alternatively, check the Acronis Management Console or service information.
    Affected if Acronis Cyber Protect 15 is found installed on the system
  2. Identify the build version
    Open the Acronis Cyber Protect console or navigate to Help > About. Record the exact build number displayed. This build number is typically a numeric value (e.g., 35929, 35979, etc.).
    Affected if The build number is lower than 35979 (any build below the fixed version)
  3. Examine log files for token exposure
    Navigate to the Acronis log directory (typically C:\ProgramData\Acronis\Logs or C:\Program Files\Acronis\Cyber Protect\Logs). Open recent log files and search for patterns resembling authentication tokens, session IDs, or credential strings. Look for unmasked token values in API responses or error messages.
    Affected if Log files contain visible authentication tokens, session IDs, or credential strings that appear unmasked
  4. Inspect UI for token masking behavior
    Access the Acronis Cyber Protect 15 administrative interface. Navigate to areas where authentication credentials, API tokens, or session data are displayed (such as backup destination configuration, integration settings, or user management). Observe whether sensitive fields show full unmasked values or display masked characters.
    Affected if The UI displays unmasked or partially visible authentication tokens or session credentials in any configuration screen

You are affected if Acronis Cyber Protect 15 is installed with a build number below 35979, or if log files or the administrative UI expose unmasked authentication tokens or session credentials.

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 Cyber Protect 15 to build 35979 or later to remediate the token field masking issue.

Recommended fix Moderate confidence

Acronis Cyber Protect 15 build 35979 or later

  1. Backup your current Acronis Cyber Protect 15 configuration and data before upgrading
  2. Download Acronis Cyber Protect 15 build 35979 or later from the official Acronis download portal or your licensed download area
  3. Follow Acronis standard upgrade procedures for Cyber Protect 15 (Linux or Windows depending on your deployment)
  4. After upgrade, verify that the token field masking is working correctly in the UI
  5. Confirm the sensitive information disclosure is resolved by checking that tokens are now properly masked
Caveat Standard patch upgrade with minimal risk; review release notes for any configuration changes

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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