Zero-Day

Critical

Zero-Day

Definition

A Zero-Day (0-day) vulnerability is a security flaw that is unknown to the software vendor and for which no patch is available. The term 'zero day' means the developer has had zero days to fix the problem. These vulnerabilities are extremely valuable both to attackers and in legitimate security markets.

Impact

With no patch available, every affected system is vulnerableHigh value in exploit markets (hundreds of thousands of euros)Used in targeted attacks and APTs (Advanced Persistent Threats)Can remain undiscovered for months or yearsMassive impact when found in widely used software

Examples

Historic Zero-Day examples

Log4Shell (CVE-2021-44228) was a zero-day in Apache Log4j that enabled RCE and affected millions of Java applications globally. Before its disclosure, it is estimated to have been actively exploited for at least two weeks. The highest-paying bug bounty programs usually pay the largest amounts for critical zero-days.

External references

Practice Zero-Day with real labs

Apply what you've learned in safe environments based on real bug bounty reports.

See practice labs
hunters training
712

hunters training

labs from real reports
55

labs from real reports

completions
1,206

completions

in bounties practiced
$213,970

in bounties practiced

46 flags captured this week·Real reports from HackerOne · Bugcrowd · Intigriti·No commitment·Free Academy
BBLabs · bug bounty training

Stop reading about bugs and start hunting them

Create your free account and practice on labs based on real reports that paid out thousands of euros. The Academy is free forever.

No card · free Academy · cancel anytime