dbcve.org
VelociraptorApplication · Rapid7

CVE-2023-5950

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to 0.6.9-1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 versions prior to 0.7.0-4 suffer from a reflected cross site scripting vulnerability. This vulnerability allows attackers to inject JS into the error path, potentially leading to unauthorized execution of scripts within a user's web browser. This vulnerability is fixed in version 0.7.0-04 and a patch is available to download. Patches are also available for version 0.6.9 (0.6.9-1).

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

Reflected cross-site scripting (XSS) vulnerability in Rapid7 Velociraptor allows attackers to inject malicious JavaScript into error handling paths. When users trigger specific error conditions, the unsanitized input is reflected back and executed in their browsers, enabling session hijacking or credential theft.

MitigationUpgrade Velociraptor to version 0.7.0-4 or apply the available patch for version 0.6.9-1. Additionally, implement input validation and output encoding on all error response paths.

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.9-1= 0.7.0= 0.7.0-3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check Velociraptor binary version
    Run 'velociraptor --version' or examine the binary file name and metadata to determine the exact installed version
    Affected if The version displayed is earlier than 0.6.9-1, or shows exactly 0.7.0 or 0.7.0-3
  2. Verify the web interface is enabled
    Check if Velociraptor is configured to run with its web UI by reviewing the server configuration file or checking for listening ports (default 8000)
    Affected if The web interface is enabled and accessible over HTTP/HTTPS
  3. Identify error handling endpoints
    Review Velociraptor server logs or documentation for error handling paths - look for endpoints that return user-supplied input in error responses
    Affected if Error endpoints exist that reflect query parameters or input back to the user without sanitization
  4. Check for unpatched dependencies
    Review the Velociraptor installation package or source code for third-party libraries used in error handling code
    Affected if Libraries related to HTTP response handling remain at vulnerable versions

A user is affected if Velociraptor version is < 0.6.9-1, = 0.7.0, or = 0.7.0-3 AND the web interface is enabled, allowing reflected XSS in error handling paths.

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.9-1 or later
Fixed in 0.6.9-1
Interim mitigation

Upgrade Velociraptor to version 0.7.0-4 or apply the available patch for version 0.6.9-1. Additionally, implement input validation and output encoding on all error response paths.

Recommended fix High confidence

0.7.0-4

  1. 1. Identify the currently installed Velociraptor version using 'velociraptor --version' or checking the server's about page
  2. 2. Download Velociraptor version 0.7.0-4 (or later) from the official GitHub releases page at github.com/Velocidex/velociraptor
  3. 3. Backup your current Velociraptor configuration, client, and server artifacts
  4. 4. Upgrade the Velociraptor server by replacing the binary and restarting the service
  5. 5. Ensure the Velociraptor GUI is accessible and verify the upgrade was successful by checking the version number
  6. 6. If using version 0.6.x, alternatively apply the patch for version 0.6.9-1 if available from GitHub
Caveat Review release notes for any configuration changes or migration requirements between your current version and 0.7.0-4

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

Fix this in Velociraptor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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