Zero-day (computing)

From HandWiki
Short description: Unfixed software vulnerability


A zero-day (also known as a 0-day) is a vulnerability or security hole in a computer system unknown to its owners, developers or anyone capable of mitigating it.[1] Until the vulnerability is remedied, threat actors can exploit it in a zero-day exploit, or zero-day attack.[2]

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.[3][4][5] 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 attacks are severe threats.[6]

Attack vectors

Potential attack vectors for a zero-day vulnerability are identical to known vulnerabilities and those that have available patches. For example, when a user visits a rogue website, malicious code on the site can exploit unpatched vulnerabilities in a Web browser. Web browsers are a particular target for criminals because of their widespread distribution and usage. Cybercriminals, as well as international vendors of spyware such as Israel’s NSO Group,[7] can also send malicious e-mail attachments via SMTP, which exploit vulnerabilities in the application opening the attachment.[8] Exploits that take advantage of common file types are numerous and frequent, as evidenced by their increasing appearances in databases such as US-CERT. Criminals can engineer malware to take advantage of these file type exploits to compromise attacked systems or steal confidential data.[9]

Window of vulnerability

The time from when a software exploit first becomes active to the time when the number of vulnerable systems shrinks to insignificance is known as the window of vulnerability.[10] The timeline for each software vulnerability is defined by the following main events:

  • t0: The vulnerability is discovered (by anyone).
  • t1a: A security patch is published (e.g., by the software vendor).
  • t1b: An exploit becomes active.
  • t2: Most vulnerable systems have applied the patch.

Thus the formula for the length of the window of vulnerability is: t2 − t1b.

In this formulation, it is always true that t0 ≤ t1a, and t0 ≤ t1b. Note that t0 is not the same as day zero. For example, if a hacker is the first to discover (at t0) the vulnerability, the vendor might not learn of it until much later (on day zero).

For normal vulnerabilities, t1b > t1a. This implies that the software vendor was aware of the vulnerability and had time to publish a security patch (t1a) before any hacker could craft a workable exploit (t1b). For zero-day exploits, t1b ≤ t1a, such that the exploit becomes active before a patch is made available.

By not disclosing known vulnerabilities, a software vendor hopes to reach t2 before t1b is reached, thus avoiding any exploits. However, the vendor has no guarantees that hackers will not find vulnerabilities on their own. Furthermore, hackers can analyze the security patches themselves, and thereby discover the underlying vulnerabilities and automatically generate working exploits.[11] These exploits can be used effectively up until time t2.

In practice, the length of the window of vulnerability varies between systems, vendors, and individual vulnerabilities. It is often measured in days, with one report from 2006 estimating the average as 28 days.[12]

Protection

Zero-day protection is the ability to provide protection against zero-day exploits. Since zero-day attacks are generally unknown to the public, it is often difficult to defend against them. Zero-day attacks are often effective even against "secure" networks and can remain undetected even after they are launched. Thus, users of so-called secure systems must also exercise common sense and practice safe computing habits.[13]

Many techniques exist to limit the effectiveness of zero-day memory corruption vulnerabilities such as buffer overflows. These protection mechanisms exist in contemporary operating systems such as macOS, Windows Vista and beyond (see Security and safety features new to Windows Vista), Solaris, Linux, Unix, and Unix-like environments; Windows XP Service Pack 2 includes limited protection against generic memory corruption vulnerabilities[14] and previous versions include even less. Desktop and server protection software also exist to mitigate zero-day buffer overflow vulnerabilities. Typically, these technologies involve heuristic termination analysis in order to stop attacks before they cause any harm.[15]

It has been suggested that a solution of this kind may be out of reach because it is algorithmically impossible in the general case to analyze any arbitrary code to determine if it is malicious: as such an analysis reduces to the halting problem over a linear bounded automaton, which is unsolvable. It is, however, unnecessary to address the general case (that is, to sort all programs into the categories of malicious or non-malicious) under most circumstances in order to eliminate a wide range of malicious behaviors. It suffices to recognize the safety of a limited set of programs (e.g., those that can access or modify only a given subset of machine resources) while rejecting both some safe and all unsafe programs. This does require the integrity of those safe programs to be maintained, which may prove difficult in the face of a kernel-level exploit.[citation needed]

The Zeroday Emergency Response Team (ZERT) was a group of software engineers who worked to release non-vendor patches for zero-day exploits.

Worms

Computer worms are intercepted using knowledge about how they infect their hosts. Zero-day worms take advantage of a surprise attack while they are still unknown to computer security professionals. Recent history shows an increasing rate of worm propagation.[16] New worms are difficult to detect, because their infection signatures are unknown, and well-designed worms can spread very quickly throughout the Internet, sometimes with devastating consequences.[17]

Ethics

Differing ideologies exist relating to the collection and use of zero-day vulnerability information. Many computer security vendors perform research on zero-day vulnerabilities in order to better understand the nature of vulnerabilities and their exploitation by individuals, computer worms and viruses. Alternatively, some vendors purchase information about vulnerabilities to augment their research capacity. An example of such a program is TippingPoint's Zero Day Initiative.

While selling and buying information about vulnerabilities is not technically illegal in most parts of the world, there is a lot of controversy over the method of disclosure. A 2006 German decision to include Article 6 of the Convention on Cybercrime and the EU Framework Decision on Attacks against Information Systems may make selling or even manufacturing vulnerabilities illegal.[18]

Most formal programs follow some form of Rain Forest Puppy's disclosure guidelines or the more recent OIS Guidelines for Security Vulnerability Reporting and Response.[citation needed] In general, these rules forbid the public disclosure of vulnerabilities without notification to the vendor and adequate time to produce a patch.

Viruses

A zero-day virus (also known as zero-day malware or next-generation malware) is a previously unknown computer virus or other malware for which specific antivirus software signatures are not yet available.[19]

Traditionally, antivirus software relied upon signatures to identify malware. A virus signature is a unique pattern or code that can be used to detect and identify specific viruses. The antivirus scans file signatures and compares them to a database of known malicious codes. If they match, the file is flagged and treated as a threat. The major limitation of signature-based detection is that it is only capable of flagging already known malware, making it useless against zero-day attacks.[20] Most modern antivirus software still uses signatures but also carries out other types of analysis.[citation needed]

Code analysis

In code analysis, the machine code of the file is analysed to see if there is anything that looks suspicious. Typically, malware has characteristic behaviour; code analysis attempts to detect if this is present in the code.

Although useful, code analysis has significant limitations. It is not always easy to determine what a section of code is intended to do, particularly if it is very complex and has been deliberately written with the intention of defeating analysis. Another limitation of code analysis is the time and resources available. In the competitive world of antivirus software, there is always a balance between the effectiveness of analysis and the time delay involved.

One approach to overcome the limitations of code analysis is for the antivirus software to run suspect sections of code in a safe sandbox and observe their behavior. This can be orders of magnitude faster than analyzing the same code, but must resist (and detect) attempts by the code to detect the sandbox.

Generic signatures

Generic signatures are signatures that are specific to certain behaviour rather than a specific item of malware. Most new malware is not totally novel, but is a variation on earlier malware, or contains code from one or more earlier examples of malware. Thus, the results of previous analysis can be used against new malware.

Competitiveness in the antivirus software industry

It is generally accepted in the antivirus industry that most vendors' signature-based protection is identically effective. If a signature is available for an item of malware, then every product (unless dysfunctional) should detect it. However, some vendors are significantly faster than others at becoming aware of new viruses and/or updating their customers' signature databases to detect them.[21]

There is a wide range of effectiveness in terms of zero-day virus protection. The German computer magazine c't found that detection rates for zero-day viruses varied from 20% to 68%.[22] It is primarily in the area of zero-day virus performance that manufacturers now compete.

U.S. government involvement

NSA's use of zero-day exploits (2017)

In mid-April 2017 the hackers known as The Shadow Brokers (TSB), who are allegedly linked to the Russian government,[23][24] released files from the NSA (initially just regarded as alleged to be from the NSA, later confirmed through internal details and by American whistleblower Edward Snowden)[25] which include a series of 'zero-day exploits' targeting Microsoft Windows software and a tool to penetrate the Society for Worldwide Interbank Financial Telecommunication (SWIFT)'s service provider.[26][27][28] Ars Technica had reported Shadow Brokers' hacking claims in mid-January 2017,[29] and in April the Shadow Brokers posted the exploits as proof.[29]

Vulnerabilities Equities Process

Main page: Vulnerabilities Equities Process

The Vulnerabilities Equities Process, first revealed publicly in 2016, is a process used by the U.S. federal government to determine on a case-by-case basis how it should treat zero-day computer security vulnerabilities: whether to disclose them to the public to help improve general computer security or to keep them secret for offensive use against the government's adversaries.[30] The process has been criticized for a number of deficiencies, including restriction by non-disclosure agreements, lack of risk ratings, special treatment for the NSA, and a less than full commitment to disclosure as the default option.[31]

See also

References

  1. ↑ Guo, Mingyu; Wang, Guanhua; Hata, Hideaki; Babar, Muhammad Ali (2021-07-01). "Revenue maximizing markets for zero-day exploits" (in en). Autonomous Agents and Multi-Agent Systems 35 (2): 36. doi:10.1007/s10458-021-09522-w. ISSN 1387-2532. https://link.springer.com/10.1007/s10458-021-09522-w. 
  2. ↑ Compare: "What is a Zero-Day Vulnerability?". Symantec. http://www.pctools.com/security-news/zero-day-vulnerability/. "A zero day vulnerability refers to an exploitable bug in software that is unknown to the vendor. This security hole may be exploited by crackers before the vendor becomes aware and hurries to fix it—this exploit is called a zero day attack." 
  3. ↑ Zetter, Kim (Nov 11, 2014). "Hacker Lexicon: What Is a Zero Day?". Wired. https://www.wired.com/2014/11/what-is-a-zero-day/. 
  4. ↑ "Where the term "Zero Day" comes from - mmmm". 2018-01-31. http://markmaunder.com/2014/06/16/where-zero-day-comes-from/. 
  5. ↑ "Flash Vulnerabilities Causing Problems". ESET. http://www.eset.co.uk/Press-Centre/Blog/Article/flash-zero-day. 
  6. ↑ The Man Who Found Stuxnet – Sergey Ulasen in the Spotlight published on November 2, 2011
  7. ↑ Ahmed, Azam; Perlroth, Nicole (19 June 2017). "Using Texts as Lures, Government Spyware Targets Mexican Journalists and Their Families". The New York Times. https://www.nytimes.com/2017/06/19/world/americas/mexico-spyware-anticrime.html. 
  8. ↑ "SANS sees upsurge in zero-day Web-based attacks". Computerworld. http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9005117. 
  9. ↑ "E-mail Residual Risk Assessment". Avinti, Inc.. p. 2. http://www.avinti.com/download/case_studies/whitepaper_email_residual_risk.pdf. 
  10. ↑ Johansen, Håvard; Johansen, Dag; Renesse, Robbert van (2007-05-14). "FirePatch: Secure and Time-Critical Dissemination of Software Patches". in Venter, Hein (in en). New Approaches for Security, Privacy and Trust in Complex Environments. IFIP International Federation for Information Processing. 232. Springer US. pp. 373–384. doi:10.1007/978-0-387-72367-9_32. ISBN 9780387723662. https://archive.org/details/newapproachesfor00hagg. 
  11. ↑ Halvar, Flake (July 2004). "Structural Comparison of Executable Objects" (in en). Proceedings of the International GI Workshop on Detection of Intrusions and Malware & Vulnerability Assessment. Lecture Notes in Informatics. P-46. Dortmund, Germany: Köllen Verlag. p. 161-174. doi:10.17877/de290r-2007. ISBN 3-88579-375-X. http://eldorado.tu-dortmund.de/handle/2003/22787. 
  12. ↑ Internet Security Threat Report. 10. Symantec Corp. September 2006. p. 12. 
  13. ↑ "What is a Zero-Day Exploit? - An introduction to zero-day software exploits and tips on avoiding them at home.". https://what-is-what.com/what_is/zero_day_exploit.html. 
  14. ↑ "Changes to Functionality in Microsoft Windows XP Service Pack 2". http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx. 
  15. ↑ "Mitigating XML Injection 0-Day Attacks through Strategy-Based Detection Systems". https://secplab.ppgia.pucpr.br/files/papers/2013-3.pdf. 
  16. ↑ "2021 has broken the record for zero-day hacking attacks" (in en). https://www.technologyreview.com/2021/09/23/1036140/2021-record-zero-day-hacks-reasons/. 
  17. ↑ Guizani, Mohsen; Rayes, Ammar; Khan, Bilal; Al-Fuqaha, Ala (26 January 2010) (in en). Network Modeling and Simulation: A Practical Perspective. John Wiley & Sons. p. 46. ISBN 978-0-470-51520-4. https://books.google.com/books?id=S5HSa3uZ8C0C&pg=PA46. 
  18. ↑ Sieber, Ulrich (2006). "International cooperation against terrorist use of the internet". Dans Revue Internationale de Detroit Pénal 77 (3–4): 13-14. https://www.cairn.info/revue-internationale-de-droit-penal-2006-3-page-395.htm. 
  19. ↑ "Cyberhawk – zero day threat detection review". http://www.kickstartnews.com/reviews/utilities/cyberhawk_zero_day_threat_detection_1.html. 
  20. ↑ "What Are Zero-Day Attacks? | Safety Detective" (in en-US). 2018-08-30. https://www.safetydetective.com/blog/what-are-zero-day. 
  21. ↑ Robert Westervelt (April 2011). "Antivirus vendors go beyond signature-based antivirus". https://searchsecurity.techtarget.com/magazineContent/Antivirus-vendors-go-beyond-signature-based-antivirus. 
  22. ↑ Goodin, Dan (21 December 2008). "Anti-virus protection gets worse". http://www.channelregister.co.uk/2007/12/21/dwindling_antivirus_protection. 
  23. ↑ "Circumstantial evidence and conventional wisdom indicates Russian responsibility. Here's why that is significant". Twitter. August 16, 2016. https://twitter.com/Snowden/status/765514891813945344. 
  24. ↑ Price, Rob. "Edward Snowden: Russia might have leaked ni9G3r alleged NSA cyberweapons as a 'warning'". http://www.businessinsider.de/edward-snowden-shadow-brokers-russia-leaked-nsa-equation-group-files-warning-dnc-hacking-2016-8. 
  25. ↑ Sam Biddle (August 19, 2016). "The NSA Leak is Real, Snowden Documents Confirm". https://theintercept.com/2016/08/19/the-nsa-was-hacked-snowden-documents-confirm/. 
  26. ↑ Henry Farrell (April 15, 2017), "Hackers have just dumped a treasure trove of NSA data. Here's what it means.", The Washington Post, https://www.washingtonpost.com/news/monkey-cage/wp/2017/04/15/shadowy-hackers-have-just-dumped-a-treasure-trove-of-nsa-data-heres-what-it-means/?tid=sm_tw, retrieved April 15, 2017 
  27. ↑ Baldwin, Clare (15 April 2017). "Hackers release files indicating NSA monitored global bank transfers". Reuters. https://www.reuters.com/article/us-usa-cyber-swift-idUSKBN17G1HC. 
  28. ↑ Lawler, Richard (15 April 2017). "Shadow Brokers release also suggests NSA spied on bank transactions". Engadget. https://www.engadget.com/2017/04/14/shadow-brokers-release-also-suggest-nsa-spied-on-bank-transactio/. 
  29. ↑ 29.0 29.1 Dan Goodin (2017-01-13). "NSA-leaking Shadow Brokers lob Molotov cocktail before exiting world stage". https://arstechnica.com/security/2017/01/nsa-leaking-shadow-brokers-lob-molotov-cocktail-before-exiting-world-stage/. 
  30. ↑ Newman, Lily Hay (2017-11-15). "Feds Explain Their Software Bug Stash—But Don't Erase Concerns" (in en-US). WIRED. https://www.wired.com/story/vulnerability-equity-process-charter-transparency-concerns/. Retrieved 2017-11-16. 
  31. ↑ McCarthy, Kieren (15 November 2017). "The four problems with the US government's latest rulebook on security bug disclosures" (in en). The Register. https://www.theregister.co.uk/2017/11/15/us_governments_vulnerability_disclosure_policy/. 

Further reading

Examples of zero-day attacks

(Chronological order)



Retrieved from "https://handwiki.org/wiki/index.php?title=Zero-day_(computing)&oldid=3372449"