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-4 and a patch is available to download. Patches are also available for version 0.6.9 (0.6.9-1)
This issue affects the server only.

Problem:

CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') CWE-79

Product Status:

References

Timeline:

• 2023-11-02 - Notification of the issue
• 2023-11-06 - Release 0.7.0-4 made available on Github

Due to insufficient validation in the PE and OLE parsers in Rapid7's Velociraptor versions earlier than 0.6.8 allows attacker to crash Velociraptor during parsing of maliciously malformed files. 

For this attack to succeed, the attacker needs to be able to introduce malicious files to the system at the same time that Velociraptor attempts to collect any artifacts that attempt to parse PE files, Authenticode signatures, or OLE files. After crashing, the Velociraptor service will restart and it will still be possible to collect other artifacts.

Problem:

CWE-125 Out-of-bounds Read CWE-125

Impact:

CAPEC-540 Overread Buffers CAPEC-540

Affected Product Status:

Solution:

Upgrade the clients to version 0.6.8-2

Improper Privilege Management vulnerability in Rapid7 Velociraptor in the copy() function.

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 (e.g. 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"). 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 and program routines copy().

This issue affects Velociraptor: before 0.6.7-5.

Required configuration for exposure:

Velociraptor deployment with multiple users at lower roles than administrators (e.g. "investigator" and above)

Problem:

CWE-269 Improper Privilege Management CWE-269

Impact:

CAPEC-75 Manipulating Writeable Configuration Files CAPEC-75

Product Status:

Solution:

Upgrade to 0.6.7-5

Workaround:

A valid workaround is to prevent the copy function in the Velociraptor allow list:

1. In the configuration wizard answer yes to the question "Do you want to restrict VQL functionality on the server?"
2. This will add a default allow list to the configuration file.
3. Copy this allow list to your existing server.config.yaml
4. Ensure the "copy" function is removed from the default allow list.

Timeline:

• 2023-01-12 - Notification of the issue
• 2023-01-17 - Release 0.6.7-5 made available on Github

Velociraptor did not properly sanitize the client id parameter to the CreateCollection API allowing a directory traversal in where the collection task could be written. It was possible to provide a client id of "../clients/server" to schedule the collection for the server (as a server artifact), but only require privileges to schedule collections on the client.

Normally to schedule an artifact on the server requires the COLLECT_SERVER permissions (normally only granted to "administrator" role), but due to this issue it is sufficient to have the COLLECT_CLIENT privilege (normally granted to the "investigator" role)

To exploit this vulnerability, the attacker must already have a Velociraptor user account at a low privilege level (not administrator but at least "investigator"). Be able to authenticate to the GUI (e.g. via OAuth2) and issue an API call to the backend. 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/services/launcher/launcher.go and program routines ScheduleArtifactCollection().

This issue affects Velociraptor: before 0.6.7-5.

Required configuration for exposure:

Velociraptor deployment with multiple users at lower roles than administrators (e.g. "investigators")

Problem:

CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') CWE-22

Impact:

CAPEC-233 Privilege Escalation CAPEC-233

Product Status:

Solution:

Upgrade to 0.6.7-5

Timeline:

• 2023-01-13 - Notification of the issue
• 2023-01-17 - Release 0.6.7-5 made available on Github