Lably
Skip to content

Zero-day vulnerability

Unfixed software vulnerability

  • 10 min read
  • 7 chapters

Related on Lably

Through Computer, Mitigation and Software

The term "zero-day" originally referred to the number of days since a new piece of software was released to the public, so "zero-day software" was obtained by hacking into a developer's computer before release. Eventually the term was applied to the vulnerabilities that allowed this hacking, and to the number of days that the vendor has had to fix them. Vendors who discover the vulnerability may create patches or advise workarounds to mitigate it, though users need to deploy that mitigation to eliminate the vulnerability in their systems. Zero-day vulnerabilities are extremely dangerous in theory because they are unknown to the developers and have no available patch. However, they are not always catastrophic in practice. Their real-world impact depends heavily on many factors.

Definition

Despite developers' goal of delivering a product that works entirely as intended, virtually all products contain software and hardware bugs. If a bug creates a security risk, it is called a vulnerability. Vulnerabilities vary in their ability to be exploited by malicious actors. Some are not usable at all, while others can be used to disrupt the device with a denial of service attack. The most dangerous allow the attacker to inject and run their own code, without the user being aware of it. Although the term "zero-day" initially referred to the time since the vendor had become aware of the vulnerability, zero-day vulnerabilities can also be defined as the subset of vulnerabilities for which no patch or other fix is available. A zero-day exploit is any exploit that takes advantage of such a vulnerability.

Sign in to keep reading

6 more chapters are free with a Lably account.

More in Computing and communication