What is a zero-day vulnerability?
A zero-day is a vulnerability the vendor does not yet know about or has not fixed. Unlike an unpatched known flaw, no fix is available, so defenders rely on layered controls and workarounds until a patch arrives.

Exam objectiveExplain various types of vulnerabilities
Objective 2.3 covers the types of vulnerabilities, weaknesses that can be exploited, grouped by where they live: in applications, in platforms, or in the trust and setup around a system.
Applications. Buffer overflows write input past the space set aside for it, and memory injection places attacker code into a running process. Race conditions, such as time-of-check to time-of-use (TOCTOU), let a resource change between a security check and its use. A malicious update turns an application's own trusted update channel into a delivery vehicle for malware. On the web, SQL injection abuses the application's database and cross-site scripting (XSS) abuses other visitors' browsers.
Platforms. Operating system flaws expose the layer under every application. Hardware weaknesses include firmware that is rarely updated and end-of-life or legacy devices. Virtualization flaws target isolation through VM escape and resource reuse. Cloud weaknesses mostly come from how customers configure their own accounts, data, and access within a shared responsibility split. Mobile devices are weakened by sideloading and jailbreaking.
Trust and setup. Supply chain vulnerabilities are weaknesses inherited from service, hardware, and software providers. Cryptographic weaknesses include obsolete or broken algorithms and weak random number generation, and misconfiguration is sound software run with wrong or excessive settings. A zero-day is a flaw the vendor does not yet know about or has not fixed.
Exam questions describe a symptom and ask for the vulnerability class. Name the mechanism first, then the fix: parameterized queries stop SQL injection, output encoding stops XSS, and atomic operations close a race window.
This page is the map. Knotch is where you drill it until it sticks.
SQL injection targets the database behind the application, on the server side. Cross-site scripting targets other visitors' browsers, on the client side; both start when untrusted input is treated as code.
A buffer overflow is a flaw in a program: input larger than its reserved space spills into neighboring memory. Memory injection is something an attacker does: placing code inside a process that is already running.
In a VM escape the attacker breaks out of a guest and crosses the isolation boundary. In resource reuse nobody breaks anything: the hypervisor hands recycled memory or storage to a new tenant with old data still in it.
A malicious update is one common way a supply chain compromise is delivered. The exam lists it as its own type, but the update is how the compromise reaches you.
The full set of look-alike pairs for this objective is inside Knotch.
On a product search page, entering an apostrophe returns a database error, and entering ' OR '1'='1 returns every row. Separately, a comments field renders <script> tags submitted by one user and runs them in other visitors' browsers.
Which pairing is correct?
Altering a server-side query is SQLi; persistent script executing in other users' browsers is stored XSS.
SQLi attacks the back-end data layer; XSS attacks other users through the browser. Parameterized queries and output encoding are the respective core defenses.
Why not B: This reverses them.
Why not C: The comments issue runs script in the browser, not in a database query.
Why not D: The search issue manipulates a database query.
A zero-day is a vulnerability the vendor does not yet know about or has not fixed. Unlike an unpatched known flaw, no fix is available, so defenders rely on layered controls and workarounds until a patch arrives.
Sideloading installs an app from outside the official store, bypassing store vetting. Jailbreaking or rooting removes the operating system's own restrictions, such as app signing and sandboxing; it often enables sideloading, but sideloading does not require it.
A race condition depends on the timing of operations and appears only when events overlap or reorder. A buffer overflow depends on how much data is written and appears when input is too big for its space.
