Velociraptor incorrect Org deletion permissions check
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Rapid7 | Velociraptor | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Rapid7 | Velociraptor |
|
Vendor Workaround
Ensure administrator users in child orgs are trusted to manage orgs.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.443% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Velociraptor allows multi-tenant deployments named "Orgs". By default Velociraptor, uses the ROOT org, but users can create child orgs for other tenants within the same deployment. Users can have different permissions in each org. To manage Orgs, Velociraptor usually examines the ORG_ADMIN permission on the ROOT org. This issue results from the Velociraptor server allowing for the deletion of Orgs by incorrectly checking the ORG_ADMIN permission of callers within the calling ORG instead of the ROOT org. However, Org admins of child orgs were able to add this permission to their ACL token within their own org. This allows an administrator in a child org, which is not also an administrator in the ROOT org, to delete other orgs. | |
| Title | Velociraptor incorrect Org deletion permissions check | |
| First Time appeared |
Rapid7
Rapid7 velociraptor |
|
| Weaknesses | CWE-280 | |
| CPEs | cpe:2.3:a:rapid7:velociraptor:*:*:linux:*:*:*:*:* | |
| Vendors & Products |
Rapid7
Rapid7 velociraptor |
|
| References |
| |
| Metrics |
cvssV3_1
|