Security
Headlines
HeadlinesLatestCVEs

Headline

CVE-2023-0242: Current CVEs :: Velociraptor - Digging deeper!

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.

CVE
#vulnerability#mac#windows#linux#git#perl#oauth#auth

The following CVEs were reported with the current 0.6.7 release. Both Vulnerabilities can result in privilege escalation from low privilege “investigator” Velociraptor users to “administrator” level.

If you use multiple roles with your Velociraptor GUI users, we recommend to upgrade your server to the 0.6.7-5 release. These issues do not affect clients so there is no need to upgrade clients.

CVE-2023-0242 Insufficient Permission Check In The VQL Copy() Function

Published on 2023-01-18

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:

Product

Affected

Rapid7 Velociraptor » VQL copy() function on Linux, Windows, MacOS, 64 bit, 32 bit
package reposource repohttps://github.com/Velocidex/velociraptor/blob/master/vql/filesystem/copy.gocopy()
Default status is unaffected

before 0.6.7-5 (unaffected from 5)

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.

Credits:

Paul Alkemade from Telstra

Timeline:

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

CVE-2023-0290 Directory Traversal In Client Id Parameter

Publishedon 2023-01-17

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:

Product

Affected

Rapid7 Velociraptor » CreateCollection API on Windows, Linux, MacOS, 64 bit, 32 bit
package reposource repohttps://github.com/Velocidex/velociraptor/blob/master/services/launcher/launcher.goScheduleArtifactCollection()
Default status is unaffected

before 0.6.7-5 (unaffected from 5)

Solution:

Upgrade to 0.6.7-5

Credits:

Paul Alkemade from Telstra

Timeline:

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

Related news

CVE-2023-0290: GitHub - Velocidex/velociraptor: Digging Deeper....

Rapid7 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, the COLLECT_SERVER permission is required. This permission is normally only granted to "administrator" role. Due to this issue, it is sufficient to have the COLLECT_CLIENT privilege, which is normally granted to the "investigator" role. To exploit this vulnerability, the attacker must already have a Velociraptor user account at least "investigator" level, and be able to authenticate to the GUI and issue an API call to the backend. Typically, most users deploy Velociraptor with limited access to a trusted group, and most users will already be administrators within the GUI. ...

CVE: Latest News

CVE-2023-50976: Transactions API Authorization by oleiman · Pull Request #14969 · redpanda-data/redpanda
CVE-2023-6905
CVE-2023-6903
CVE-2023-6904
CVE-2023-3907