dbcve.org
CWE-552Weakness · CWE-552

CVE-2024-10526

HIGH · 8.6 CVSS v4.0 Published 2024-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High

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
Rapid7 Velociraptor MSI Installer versions below 0.73.3 suffer from a vulnerability whereby it creates the installation directory with WRITE_DACL permission to the BUILTIN\\Users group. This allows local users who are not administrators to grant themselves the Full Control permission on Velociraptor's files. By modifying Velociraptor's files, local users can subvert the binary and cause the Velociraptor service to execute arbitrary code as the SYSTEM user, or to replace the Velociraptor binary completely.  This issue is fixed in version 0.73.3.

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

The Rapid7 Velociraptor MSI Installer versions prior to 0.73.3 creates the installation directory with WRITE_DACL permissions granted to the BUILTIN\Users group. This allows any local non-privileged user to modify access control permissions on the directory contents, enabling them to grant themselves Full Control and modify or replace Velociraptor executable files. Since the Velociraptor service runs as SYSTEM, a local attacker can achieve privilege escalation by subverting the binary.

MitigationUpgrade Velociraptor MSI Installer to version 0.73.3 or later. For existing installations, manually correct directory permissions to remove excessive BUILTIN\Users access and verify integrity of executable files.

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
Authentication
Y
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:D/RE:L/U:Red

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. Locate Velociraptor installation directory
    Check common installation paths such as C:\Program Files\Velociraptor, C:\Program Files (x86)\Velociraptor, or review registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the Velociraptor entry to find the InstallLocation value
    Affected if Velociraptor is found installed on the system
  2. Determine installed Velociraptor version
    Right-click on velociraptor.exe in the installation directory, select Properties, and view the File version on the Details tab. Alternatively, run 'velociraptor.exe --version' from an elevated command prompt if the binary is accessible
    Affected if The version number is lower than 0.73.3 (for example, 0.73.2, 0.72.x, etc.)
  3. Check BUILTIN\Users permissions on installation directory
    Right-click the Velociraptor installation folder in Explorer, select Properties, go to the Security tab, and examine the permissions for the Users group. Alternatively, run 'icacls "<install_path>"' from an elevated command prompt to list all ACL entries
    Affected if The Users group (BUILTIN\Users) is listed with WRITE, MODIFY, or FULL CONTROL permissions on the installation directory
  4. Verify if non-privileged users can modify executable files
    As a standard (non-admin) user, attempt to delete or rename a file in the Velociraptor installation directory, such as velociraptor.exe or any .exe/.dll file in that folder
    Affected if The operation succeeds or does not return an Access Denied error, confirming the directory is writable by low-privileged users

The system is affected if Velociraptor version is below 0.73.3 AND the installation directory grants WRITE or MODIFY permissions to the BUILTIN\Users group, allowing non-privileged users to replace service executables.

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 Velociraptor MSI Installer to version 0.73.3 or later. For existing installations, manually correct directory permissions to remove excessive BUILTIN\Users access and verify integrity of executable files.

Recommended fix High confidence

0.73.3

  1. Download Velociraptor MSI Installer version 0.73.3 or later from the official Velociraptor distribution site (docs.velociraptor.app)
  2. If Velociraptor is currently installed, stop the Velociraptor service to avoid file lock conflicts
  3. Uninstall the current vulnerable version of Velociraptor using Windows Programs and Features or msiexec /x {product-code
  4. Install the downloaded fixed version (0.73.3 or later) by running the MSI installer with appropriate privileges
  5. Verify the installation completed successfully and the service starts correctly
  6. Confirm the installation directory permissions no longer grant WRITE_DACL to BUILTIN\Users group

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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