Zero-day vulnerability: Difference between revisions

Revision as of 17:23, 17 January 2023

The JC’s amateur guide to systems theory™

Index: Click ᐅ to expand: Systems theory The Devil’s Advocate

Tell me more Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

Zero-day vulnerability
/ˈzɪərəʊ-deɪ ˌvʌlnərəˈbɪlɪti/ ('.)

A vulnerability in code that hackers find before the software vendor does. Because the vendor is none-the-wiser, there is no patch for the bug, meaning until the vendor (a) twigs that there’s a problem, (b) works out how to fix it and (c) rolls the patch out to its customers, hackers who know about it can have a field-day.

@@ Line 1: / Line 1: @@
 {{a|systems|}}{{d|{{PAGENAME}}|/ˈzɪərəʊ-deɪ ˌvʌlnərəˈbɪlɪti/|}}
-A vulnerability in code that hackers find before the software vendor has become aware of it. Because the vendor are unaware, no patch exists for zero-day vulnerabilities, making attacks likely to succeed.
+A vulnerability in code that hackers find before the software vendor does. Because the vendor is none-the-wiser, there is no patch for the bug, meaning until the vendor (a) twigs that there’s a problem, (b) works out how to fix it and (c) rolls the patch out to its customers, hackers who know about it can have a field-day.

Zero-day vulnerability: Difference between revisions

Revision as of 17:23, 17 January 2023

Navigation menu

Search