dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-48683

HIGH · 7.1 CVSS v3.0 Published 2024-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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 and manipulation due to missing authorization. The following products are affected: Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows) before build 37758, Acronis Cyber Protect 16 (Linux, macOS, Windows) before build 39169.

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

Missing authorization in Acronis Cyber Protect Cloud Agent and Cyber Protect 16 allows unauthorized users to access or manipulate sensitive information. This vulnerability affects Linux, macOS, and Windows versions before the specified build numbers (37758 and 39169 respectively).

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 37758 or later, and Acronis Cyber Protect 16 to build 39169 or later to implement proper authorization controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 agent is installed
    On Windows: Check Program Files for 'Acronis' folder or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Acronis*'}'; On Linux: Run 'rpm -qa | grep -i acronis' or 'dpkg -l | grep -i acronis'; On macOS: Run 'ls /Applications | grep -i acronis' or 'system_profiler SPApplicationsDataType | grep -i acronis'
    Affected if No Acronis product is found, meaning the system is not running this software
  2. Identify the specific Acronis product installed
    On Windows: Check registry key 'HKLM\Software\Acronis' for 'Product' or 'MotiveProductName' value; On Linux/macOS: Run 'rpm -qi <acronis-package>' or 'pkgutil --info com.acronis.*' to determine if it is Cyber Protect Cloud Agent or Cyber Protect 16
    Affected if Product cannot be determined as either Cyber Protect Cloud Agent or Cyber Protect 16
  3. Determine the installed build version
    On Windows: Check registry 'HKLM\Software\Acronis\MMS\Configuration\Build' or inspect file 'C:\ProgramData\Acronis\Agent\info.json' for 'build' field; On Linux: Run 'rpm -qi acronis-agent' or check '/var/lib/Acronis/build_info.xml'; On macOS: Check '/Library/Application Support/Acronis/Agent/config/build' or right-click Acronis in Applications > Get Info
    Affected if Build version cannot be retrieved or is below 37758 for Cloud Agent or below 39169 for Cyber Protect 16
  4. Confirm the platform is affected
    Verify the operating system is Linux, macOS, or Windows by running 'uname -a' (Linux/macOS) or 'winver' (Windows). Cross-reference with the detected product version.
    Affected if Platform is Linux, macOS, or Windows AND the Acronis build is below the fixed version thresholds

A system is affected if Acronis Cyber Protect Cloud Agent (any build below 37758) or Cyber Protect 16 (any build below 39169) is installed on Linux, macOS, or Windows.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Acronis Cyber Protect Cloud Agent to build 37758 or later, and Acronis Cyber Protect 16 to build 39169 or later to implement proper authorization controls.

Recommended fix High confidence

Acronis Cyber Protect Cloud Agent: build 37758 or later; Acronis Cyber Protect 16: build 39169 or later

  1. Identify the currently installed Acronis product (Cyber Protect Cloud Agent or Cyber Protect 16) and its current build version
  2. For Acronis Cyber Protect Cloud Agent: Upgrade to build 37758 or later for Linux, macOS, and Windows
  3. For Acronis Cyber Protect 16: Upgrade to build 39169 or later for Linux, macOS, and Windows
  4. Verify the upgrade was successful by checking the new build version in the product UI or via command line
  5. Test that the authorization controls are functioning correctly after upgrade
Caveat Review Acronis release notes for the target build for any compatibility or configuration changes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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