Rapid7 Velociraptor directory traversal in client ID parameter
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2023-0290
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 09:25 UTC · Revision 1
Source evidence
Rapid7 Velociraptor directory traversal in client ID parameter
core-osv · Original sourcePublished 18 Jan 2023, 21:10 UTC
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.
osv:CVE-2023-0290
Complete source record
{
"id": "ced68850ab7ae843990fd8987347536b368b1c9b517101499368769c3341fa9b",
"url": "https://osv.dev/vulnerability/CVE-2023-0290",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Rapid7 Velociraptor directory traversal in client ID parameter",
"summary": "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.",
"evidence": "osv:CVE-2023-0290",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2023-0290",
"aliases": [
"CVE-2023-0290",
"GHSA-7jf5-fvgf-48c6",
"GO-2023-1502"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/velocidex/velociraptor",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "4718bb0cb426564568abc77910e90a2c211a32e6"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "0.6.7-5"
}
],
"source": "DESCRIPTION"
},
{
"cpe": "cpe:2.3:a:rapid7:velociraptor:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "0.6.7-5"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v0.6.7-4",
"v0.6.7-3",
"v0.6.7-1",
"v0.6.7-rc3",
"v0.6.7-rc1",
"v0.6.4-rc1",
"v0.6.3-rc1",
"v0.6.2-rc1",
"v0.6.1-rc1",
"v0.6.0-rc1",
"v0.5.9-rc1",
"v0.5.8-rc1",
"v0.5.7",
"v0.5.6",
"v0.5.5-1",
"v0.5.5",
"v0.5.4",
"v0.5.3",
"v0.5.2",
"v0.5.1",
"v0.5.0",
"v0.4.9",
"v0.4.8",
"v0.4.7",
"v0.4.6",
"v0.4.5",
"v0.4.4",
"v0.4.3",
"v0.4.2",
"v0.4.1",
"v0.4.0",
"v0.3.9",
"v0.3.8",
"v0.3.7",
"v0.3.6",
"v0.3.5",
"v0.3.4",
"v0.3.3",
"v0.3.2",
"v0.3.1",
"v0.3.0",
"0.2.9",
"0.2.8",
"0.2.7",
"0.2.6",
"0.2.5",
"0.2.4",
"0.2.3",
"0.2.2",
"0.2.1",
"v0.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-0290.json"
}
}
],
"modified": "2026-10-28T02:30:46.843786138Z",
"provider": "osv",
"references": [
"https://github.com/Velocidex/velociraptor/",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/0xxx/CVE-2023-0290.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-0290",
"https://github.com/Velocidex/velociraptor",
"https://github.com/Velocidex/velociraptor/releases"
],
"provider_metadata": {
"cwe_ids": [
"CWE-22"
],
"cna_assigner": "rapid7",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"fixed": "5"
}
],
"source": "AFFECTED_FIELD",
"strategy": "ChangesAt"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/0xxx/CVE-2023-0290.json"
}
},
"related_cves": [
{
"value": "CVE-2023-0290",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 515074,
"published_at": "2023-01-18T21:10:42.929+00:00"
}