dbcve.org
VelociraptorApplication · Rapid7

CVE-2023-2226

MEDIUM · 5.3 CVSS v3.1 Published 2023-04-21
Fix available
A fix is available. Upgrade to 0.6.8 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Due to insufficient validation in the PE and OLE parsers in Rapid7's Velociraptor versions earlier than 0.6.8 allows attacker to crash Velociraptor during parsing of maliciously malformed files.  For this attack to succeed, the attacker needs to be able to introduce malicious files to the system at the same time that Velociraptor attempts to collect any artifacts that attempt to parse PE files, Authenticode signatures, or OLE files. After crashing, the Velociraptor service will restart and it will still be possible to collect other artifacts.

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 confidence

This is a denial-of-service vulnerability in Rapid7's Velociraptor forensic collection tool. The PE (Portable Executable) and OLE (Object Linking and Embedding) parsers lack sufficient input validation, allowing malformed files to crash the Velociraptor service during artifact collection. An attacker must introduce malicious files to the system concurrently with Velociraptor attempting to collect PE, Authenticode, or OLE parsing artifacts.

MitigationUpgrade Velociraptor to version 0.6.8 or later to obtain the patched parsers with proper input validation. No workarounds are mentioned in the advisory.

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
VelociraptorApplication
Affected:< 0.6.8

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Velociraptor version
    Run `velociraptor --version` or inspect the Velociraptor binary file properties
    Affected if The installed version is less than 0.6.8
  2. Identify active PE parsing artifacts
    Review Velociraptor artifact configurations or running collections for artifacts that parse PE (Portable Executable) files
    Affected if PE parsing artifacts such as Windows.System.TaskScheduler or similar PE inspection artifacts are configured for collection
  3. Identify active Authenticode artifacts
    Review artifact definitions for Authenticode-related collectors (e.g., Windows.Sys.Authenticode)
    Affected if Authenticode parsing artifacts are enabled or scheduled for collection
  4. Identify active OLE parsing artifacts
    Review artifact definitions for OLE (Object Linking and Embedding) document parsers
    Affected if OLE parsing artifacts such as Office.XML or MSOffice document collectors are enabled or scheduled for collection
  5. Assess file injection exposure
    Evaluate whether untrusted or attacker-controlled files can be placed in directories that Velociraptor scans during artifact collection
    Affected if Untrusted users can introduce maliciously crafted PE or OLE files to paths monitored by Velociraptor parsers

You are affected if Velociraptor version is below 0.6.8 AND any PE, Authenticode, or OLE parsing artifacts are configured for collection on a system where untrusted files can be introduced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.6.8 or later
Fixed in 0.6.8
Interim mitigation

Upgrade Velociraptor to version 0.6.8 or later to obtain the patched parsers with proper input validation. No workarounds are mentioned in the advisory.

Recommended fix High confidence

Velociraptor 0.6.8

  1. 1. Back up your current Velociraptor configuration and any custom artifacts.
  2. 2. Download Velociraptor version 0.6.8 or later from the official GitHub releases page (github.com/Velocidex/velociraptor).
  3. 3. Stop the Velociraptor service on your server/client systems.
  4. 4. Replace the existing Velociraptor binary with the new version 0.6.8 binary.
  5. 5. Start the Velociraptor service and verify it runs without crashing.
  6. 6. Test artifact collection for PE files, Authenticode signatures, and OLE files to confirm the parsers handle malformed input correctly without crashing.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Velociraptor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-2226 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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