Zero-Day Vulnerability
Also called 0-day.
A flaw exploited before a patch or public knowledge exists.
What it is
A vulnerability that is unknown to the vendor or unpatched at the time it is exploited, leaving defenders zero days to prepare a fix. Exploitation may precede any public disclosure.
Why it matters
Zero-days are prized by advanced actors precisely because no signature or patch yet exists, making behavioral detection essential. A confirmed zero-day reshapes incident scope and disclosure obligations.
In practice
An intrusion uses a previously unknown memory-corruption bug in a public-facing service for which no update is available.
What to look for
- Behavior detections firing with no matching signature.
- Exploitation of fully patched systems.
- Vendor emergency advisories and out of band patches.
Common mistake
Waiting for a patch to act. Mitigate, monitor and limit exposure first.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
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
- Remote Code Execution: Running attacker code on a target over a network.
- Responsible Disclosure: Reporting a flaw privately and giving time to fix before going public.
- Vulnerability Scanning: Automated probing of systems for known weaknesses.