CyberKit

Bring Your Own Vulnerable Driver

Also called BYOVD.

Loading a legitimate but flawed driver to reach the kernel.

What it is

Installing a legitimately signed but vulnerable kernel driver and then exploiting its flaw to gain kernel-level execution or to disable protections. The driver is trusted by the OS, so loading it raises few alarms by itself.

Why it matters

Kernel access lets attackers terminate protected security processes, tamper with the OS, and hide deeply, defeating user-mode defenses. Monitoring for the loading of known-vulnerable drivers is a key, high-value detection.

In practice

A known-vulnerable signed driver is dropped and loaded specifically so the attacker can kill the endpoint agent that user-mode methods could not touch.

What to look for

  • A new kernel driver service, especially one on the vulnerable driver blocklist.
  • Driver files dropped in temp or user folders.
  • Security processes terminated right after a driver loads.

Common mistake

Trusting a driver because it is signed. These drivers are genuine and signed; the flaw is what the attacker wants.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • CrowdStrike Falcon Commercial

    An EDR agent that records process, file and network activity on each host and flags this kind of behavior.

  • Microsoft Defender for Endpoint Commercial

    Microsoft's EDR, with advanced hunting tables you can query for this activity across Windows, macOS and Linux.

  • Velociraptor Open source

    Collects and hunts for artifacts across many hosts at once, often during live response. Our notes.

  • Sysmon Free

    Free Windows logging of process starts, network connections and more, which many detections rely on. Our notes.

Read next

Sources