Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: potential Go vuln in github.com/Velocidex/velociraptor: CVE-2023-0290 #1502

Closed
GoVulnBot opened this issue Jan 18, 2023 · 3 comments
Assignees
Labels
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.

Comments

@GoVulnBot
Copy link

CVE-2023-0290 references github.com/Velocidex/velociraptor, which may be a Go module.

Description:
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. This issue affects Velociraptor versions before 0.6.7-5. Version 0.6.7-5, released January 16, 2023, fixes the issue.

References:

Cross references:
No existing reports found with this module or alias.

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: github.com/Velocidex/velociraptor
    packages:
      - package: Velociraptor
description: |
    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. This issue affects Velociraptor versions before 0.6.7-5. Version 0.6.7-5, released January 16, 2023, fixes the issue.
cves:
  - CVE-2023-0290
references:
  - web: https://github.com/Velocidex/velociraptor

@julieqiu julieqiu added the excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module. label Jan 25, 2023
@julieqiu julieqiu self-assigned this Jan 30, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/464316 mentions this issue: data/excluded: batch add excluded reports

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/592759 mentions this issue: data/reports: unexclude 75 reports

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/606781 mentions this issue: data/reports: unexclude 20 reports (1)

gopherbot pushed a commit that referenced this issue Aug 20, 2024
  - data/reports/GO-2023-1270.yaml
  - data/reports/GO-2023-1283.yaml
  - data/reports/GO-2023-1285.yaml
  - data/reports/GO-2023-1291.yaml
  - data/reports/GO-2023-1292.yaml
  - data/reports/GO-2023-1294.yaml
  - data/reports/GO-2023-1377.yaml
  - data/reports/GO-2023-1388.yaml
  - data/reports/GO-2023-1449.yaml
  - data/reports/GO-2023-1461.yaml
  - data/reports/GO-2023-1462.yaml
  - data/reports/GO-2023-1463.yaml
  - data/reports/GO-2023-1465.yaml
  - data/reports/GO-2023-1468.yaml
  - data/reports/GO-2023-1469.yaml
  - data/reports/GO-2023-1471.yaml
  - data/reports/GO-2023-1492.yaml
  - data/reports/GO-2023-1502.yaml
  - data/reports/GO-2023-1504.yaml
  - data/reports/GO-2023-1509.yaml

Updates #1270
Updates #1283
Updates #1285
Updates #1291
Updates #1292
Updates #1294
Updates #1377
Updates #1388
Updates #1449
Updates #1461
Updates #1462
Updates #1463
Updates #1465
Updates #1468
Updates #1469
Updates #1471
Updates #1492
Updates #1502
Updates #1504
Updates #1509

Change-Id: Ic7939af0290afe43600530ce10f5af9f2a0f7408
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/606781
Reviewed-by: Damien Neil <[email protected]>
Auto-Submit: Tatiana Bradley <[email protected]>
LUCI-TryBot-Result: Go LUCI <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
Projects
None yet
Development

No branches or pull requests

3 participants