Zero-day vulnerability: Difference between revisions
Jump to navigation
Jump to search
Amwelladmin (talk | contribs) (Created page with "{{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. Becau...") |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{a|systems|}}{{d|{{PAGENAME}}|/ˈzɪərəʊ-deɪ ˌvʌlnərəˈbɪlɪti/|}} | {{a|systems|}}{{d|{{PAGENAME}}|/ˈzɪərəʊ-deɪ ˌvʌlnərəˈbɪlɪti/|}} | ||
A vulnerability in code that hackers find before the software vendor | |||
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. | |||
Revision as of 17:23, 17 January 2023
|
The JC’s amateur guide to systems theory™
|
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.