dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-34011

MEDIUM · 6.8 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 →
68/100
Remediation priority · Elevated

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
Local privilege escalation due to insecure folder permissions. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows) before build 37758.

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

A local privilege escalation vulnerability exists in Acronis Cyber Protect Cloud Agent for Windows due to insecure folder permissions. An attacker with local access could potentially exploit misconfigured permissions on certain folders to elevate their privileges from a standard user to administrator. The vulnerability affects versions before build 37758.

MitigationUpdate Acronis Cyber Protect Cloud Agent to build 37758 or later to remediate the insecure folder permissions issue.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L

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 Cloud Agent is installed
    Open Programs and Features in Control Panel or use 'Get-ItemProperty' in PowerShell to list installed software and look for 'Acronis Cyber Protect Cloud Agent' or similar Acronis protection agent entries
    Affected if The software is present on the system
  2. Determine the installed build version
    Check the agent's build number - this is typically visible in the agent's UI under About/Help, or can be retrieved via PowerShell by querying the Acronis service information or registry keys under HKLM\SOFTWARE\Acronis
    Affected if The build number is below 37758 (versions before this build are vulnerable)
  3. Identify Acronis installation directories
    Locate the main Acronis installation folder, typically found under C:\Program Files\Acronis or C:\Program Files (x86)\Acronis, and note all subfolders used by the protection agent
    Affected if The agent is installed in standard locations and vulnerable folders exist
  4. Inspect folder permissions on Acronis directories
    Right-click each Acronis folder, go to Properties > Security, and examine the permissions for Users or Standard users group. Check if they have Write, Modify, or Full Control permissions on folders that should be restricted to administrators
    Affected if Standard user accounts have Write or Modify access to folders that should be protected (this is the vulnerable configuration)
  5. Confirm version is in affected range
    Cross-reference the identified build number with the affected range: versions before build 37758 are vulnerable
    Affected if The installed build is lower than 37758 AND insecure folder permissions exist

The environment is affected if Acronis Cyber Protect Cloud Agent for Windows is installed with a build number below 37758 and standard users have elevated permissions on Acronis directories.

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

Update Acronis Cyber Protect Cloud Agent to build 37758 or later to remediate the insecure folder permissions issue.

Recommended fix High confidence

Acronis Cyber Protect Cloud Agent (Windows) build 37758 or later

  1. Identify the current build version of Acronis Cyber Protect Cloud Agent (Windows) installed on affected systems
  2. If the installed build is earlier than 37758, download and install Acronis Cyber Protect Cloud Agent build 37758 or later from the official Acronis portal or update server
  3. Verify the upgrade was successful by checking that the agent build number is now 37758 or higher
  4. After upgrade, confirm that the folder permissions have been corrected by reviewing the installation directory permissions

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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