Zero-Day Exploits - Attacks Before Patches Exist
About 2 min read
A zero-day attack is an attack that exploits a software vulnerability during the window between when the vulnerability is discovered and when a fix patch is released. The name comes from the fact that developers have "zero days" of lead time from becoming aware of the vulnerability to deploying countermeasures. Because no known signature exists, matching against signatures alone cannot detect it. According to an analysis by Google Threat Intelligence Group (GTIG), 75 zero-day vulnerabilities were exploited in the wild in 2024, fewer than the 98 in 2023 but more than the 63 in 2022.
What Gets Decided While Waiting for a Fix
While no fix is available, the moves that can be taken run not in the direction of adding protection but in the direction of narrowing what can be used. Restricting the routes that reach it, halting the function, or limiting who may deal with it all cut into the intended use, so if the part cut away is needed for the work, the measure cannot be sustained for long. What is at issue when deciding an interim measure is therefore not its strength but how many days the restriction can be endured and, once it cannot, which part is restored first. Next, the moment of disclosure is a different moment from when use began. Disclosure marks when something became known; whether it was already in use before that cannot be read off from the disclosure. The order of the two can sometimes be established only by looking back afterwards at the records that remain. The work that starts upon disclosure therefore divides in two, preparing for what is coming and checking whether it had already come, and doing only the former leaves the latter undone. And a measure that stops things according to how they appear is no substitute for a fix, yet it is not wasted either. The useful life of such a clue is short, however: as long as there is room to produce the same result in a different appearance, what can be stopped is limited to the shape currently visible. Because the role of this measure is to secure time until the fix arrives, unless what will be advanced with that time is decided at the same moment, the measure stays in place and the actual fix is pushed back.
Zero-Day Attack Timeline
Historical Background
Stuxnet is malware that was found in 2010; an analysis report by Symantec described it as the first to exploit four zero-day vulnerabilities and concluded that its ultimate goal was to sabotage a specific industrial control system likely in Iran by reprogramming its programmable logic controllers (PLCs). In 2021, Log4Shell (the Log4j vulnerability) was added to the US CISA catalog of known exploited vulnerabilities on December 10, 2021, the same day it was published in the NVD.
Characteristics of Zero-Day Attacks
Zero-day vulnerabilities are traded at high prices on the dark web and are also used in state-level cyberattacks. Even after discovering a vulnerability, attackers may keep it secret and exploit it covertly over a long period.
How to Think About Defense
A common misconception is that "zero-day attacks can't be prevented, so countermeasures are pointless." While complete prevention is difficult, defense in depth can reduce the damage. Setting a unique, strong password for each service and enabling two-factor authentication is one of the measures against account takeover when a vulnerability is exploited. Enabling automatic software updates and applying patches promptly once they are released are also among the measures.
Was this article helpful?
Related Terms
- Security Vulnerabilities - How Flaws Get ExploitedA vulnerability is a weakness in software or configuration that attackers can exploit. Learn how scanning, patching, and secure coding reduce exposure.
- CSRF - Cross-Site Request Forgery ExplainedCSRF tricks your browser into sending unauthorized requests while you are logged in. Learn how anti-CSRF tokens and SameSite cookies prevent this attack.
- Fileless Malware - Attacks That Leave No FilesFileless malware operates in memory or abuses legitimate system tools, leaving no traditional file artifacts. It evades signature-based antivirus, and behavioral detection is one way to identify it.
- Breach Notification - Reporting Data LeaksBreach notification is the obligation to inform affected individuals and authorities after a data leak. GDPR requires notification within 72 hours; delays risk fines and loss of trust.