CVE-2022-35629
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDue 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVelociraptor before 0.6.5-2 had a validation bug in client-server communication where an authenticated client could spoof messages claiming to originate from a different client ID, allowing unauthorized actions or data access on behalf of the impersonated client.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.6.5-2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine Velociraptor server versionRun `velociraptor --version` on the server host or check the installed package version through your system's package managerAffected if The version number is less than 0.6.5-2
-
Identify if client-server communication is enabledReview the Velociraptor server configuration for active client listener configurations, typically found in server.yaml or through `velociraptor config show`Affected if Client listeners are configured and active, allowing client connections to the server
-
Inspect server logs for client impersonation signsSearch Velociraptor server logs for entries where client message source IDs do not match expected patterns, or where rapid client ID changes occur within single sessionsAffected if Log entries show client messages with mismatched or unexpected client ID signatures, or multiple client IDs associated with single authentication sessions
Your environment is affected if Velociraptor version is below 0.6.5-2 and the server has active client-server communication enabled, as the validation flaw allows authenticated clients to impersonate other client IDs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.6.5-2
Upgrade Velociraptor to version 0.6.5-2 or later. Review server logs for any suspicious client impersonation activity during the vulnerable period.
Velociraptor 0.6.5-2
- Back up your Velociraptor configuration, databases, and any custom configurations before proceeding
- Download Velociraptor version 0.6.5-2 from the official GitHub releases page (https://github.com/Velocidex/velociraptor/releases)
- Stop the running Velociraptor service on both server and clients
- Replace the Velociraptor binary with the new version 0.6.5-2
- Restart the Velociraptor server service
- Verify the server is running the fixed version using 'velociraptor --version'
- Deploy the updated client binary to all registered clients
- Verify client connectivity and proper registration with the server
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-35629 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data