Velociraptor OIDC Authenticator susceptible to email spoofing
When Velociraptor is configured to use an OIDC IdP for authentication, it uses the email claim as a username.
9 records
When Velociraptor is configured to use an OIDC IdP for authentication, it uses the email claim as a username.
Any authenticated Velociraptor user — including one holding only the readerrole — can terminate the entire server process with a single request, by calling SetPassword with a username that does not exist.
The NewNotebook API does not sufficiently sanitize its parameters allowing an authenticated user with NOTEBOOK_EDIT permission to write the notebook record outside the org's data store directory.
Velociraptor allows multi-tenant deployments named "Orgs".
Velociraptor's NTFS parsing library mishandles several out of bound and memory exhaustion bugs which may be triggered by maliciously crafted NTFS images.
The Velociraptor gRPC API has a VFSGetBuffer endpoint which allows reading files from the datastore.
Velociraptor's VQL has a query() plugin which allows running a VQL query in a different org or user context.
An authenticated attacker can spoof another GUI user's identity by sending their request with the custom header \"Grpc-Metadata-USER\".
Missing authorization check in the upload_azure, upload_sftp, and upload_smb VQL plugins allows an authenticated analyst-role user can initiate attacker-controlled outbound network connections from the Velociraptor serve…