dbcve.org
Cyber ProtectApplication · Acronis

CVE-2023-48678

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-27
Fix available
A fix is available. Upgrade to 16 or later.
See remediation →
57/100
Remediation priority · Elevated
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 insecure folder permissions. The following products are affected: Acronis Cyber Protect 16 (Linux, Windows) before build 37391.

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

Acronis Cyber Protect 16 before build 37391 contains insecure folder permissions that allow local, low-privilege users to access sensitive files or data that should be restricted. This information disclosure vulnerability stems from improper access control configurations on specific directories within the product's installation.

MitigationUpgrade to Acronis Cyber Protect 16 build 37391 or later, which contains corrected folder permission settings. Alternatively, apply vendor-supplied security patches and manually harden folder permissions on affected systems following vendor guidance.

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:< 16

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify Acronis Cyber Protect 16 is installed
    Check for Acronis Cyber Protect installation by looking in standard program directories or checking installed programs list. Common paths include C:\Program Files\Acronis or C:\Program Files (x86)\Acronis on Windows, or /opt/acronis on Linux.
    Affected if Acronis Cyber Protect 16 is found installed on the system
  2. Determine the installed build version
    Locate the Acronis Cyber Protect version information. On Windows, this is often available in Add/Remove Programs, the product's About dialog, or in version files within the installation directory. On Linux, check the installed rpm/deb package version or run the product's version command if available.
    Affected if The build number is lower than 37391 (or the version is reported as 'before build 37391' or similar)
  3. Inspect folder permissions on the installation directory
    Use native OS permission checking tools. On Windows, use icacls or accesschk to examine permissions on the Acronis installation folder and subdirectories. On Linux, use ls -la or getfacl to review folder permissions. Look for permissions that grant Read or Write access to Users, Everyone, or other low-privilege groups.
    Affected if Low-privilege users (non-admin, non-root) have unnecessary Read or Write access to sensitive directories within the Acronis installation folder

A system is affected if Acronis Cyber Protect 16 is installed with a build number below 37391 AND the installation directory has overly permissive folder access controls that allow low-privileged users to access sensitive files.

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 16 or later
Fixed in 16
Interim mitigation

Upgrade to Acronis Cyber Protect 16 build 37391 or later, which contains corrected folder permission settings. Alternatively, apply vendor-supplied security patches and manually harden folder permissions on affected systems following vendor guidance.

Recommended fix High confidence

Acronis Cyber Protect 16 build 37391 or later

  1. Check the current installed build version of Acronis Cyber Protect 16
  2. Download Acronis Cyber Protect 16 build 37391 or later from the official Acronis download center or your licensed vendor portal
  3. Apply the update following standard Acronis upgrade procedures for your operating system (Linux or Windows)
  4. Verify the installation completed successfully and confirm the new build version

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
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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