dbcve.org
VelociraptorApplication · Rapid7

CVE-2023-0242

HIGH · 8.8 CVSS v3.1 Published 2023-01-18
Fix available
A fix is available. Upgrade to 0.6.7-5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Rapid7 Velociraptor allows users to be created with different privileges on the server. Administrators are generally allowed to run any command on the server including writing arbitrary files. However, lower privilege users are generally forbidden from writing or modifying files on the server. The VQL copy() function applies permission checks for reading files but does not check for permission to write files. This allows a low privilege user (usually, users with the Velociraptor "investigator" role) to overwrite files on the server, including Velociraptor configuration files. To exploit this vulnerability, the attacker must already have a Velociraptor user account at a low privilege level (at least "analyst") and be able to log into the GUI and create a notebook where they can run the VQL query invoking the copy() VQL function. Typically, most users deploy Velociraptor with limited access to a trusted group (most users will be administrators within the GUI). This vulnerability is associated with program files https://github.Com/Velocidex/velociraptor/blob/master/vql/filesystem/copy.go https://github.Com/Velocidex/velociraptor/blob/master/vql/filesystem/copy.go and program routines copy(). This issue affects Velociraptor versions before 0.6.7-5. Version 0.6.7-5, released January 16, 2023, fixes the issue.

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

Velociraptor's VQL copy() function performs permission checks for reading files but fails to validate write permissions, allowing low-privilege users (investigator role or above) to overwrite server-side files including configuration files. An attacker with GUI access and ability to create notebooks can exploit this by invoking the copy() VQL function to write to arbitrary paths on the server.

MitigationUpgrade Velociraptor to version 0.6.7-5 or later, which was released January 16, 2023 and contains the fix for this vulnerability.

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
VelociraptorApplication
Affected:< 0.6.7-5

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Determine Velociraptor version
    Run 'velociraptor --version' or check the server's installed package version
    Affected if Version is below 0.6.7-5
  2. Verify GUI is enabled
    Check server configuration file (typically velociraptor.yaml or velociraptor.config.yaml) for 'GUI' section and http_bind_address settings
    Affected if GUI is accessible (http/https binding exists)
  3. Confirm user roles with notebook access
    Review user role assignments in the GUI under 'Users' or check the configuration for roles assigned to non-admin users. Look for roles: 'investigator', 'analyst', 'reader', or custom roles with notebook permissions
    Affected if Any user账户 has investigator role or above and can create notebooks

User is affected if Velociraptor version is below 0.6.7-5 AND the GUI is accessible with users having investigator role or higher who can create notebooks.

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

Upgrade Velociraptor to version 0.6.7-5 or later, which was released January 16, 2023 and contains the fix for this vulnerability.

Recommended fix High confidence

0.6.7-5 or later

  1. Backup your current Velociraptor configuration and any custom configurations or artifacts
  2. Download Velociraptor version 0.6.7-5 or later from the official releases (e.g., https://github.com/Velocidex/velociraptor/releases)
  3. Stop the running Velociraptor service
  4. Replace the existing Velociraptor binary with the new version
  5. Restart the Velociraptor service
  6. Verify the upgrade was successful by checking the server version in the GUI or via command line
  7. Ensure low-privilege users (investigator/analyst roles) can no longer use the copy() VQL function to write to server files

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

Fix this in Velociraptor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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