2.3 Types of Vulnerabilities

Application vulnerabilities refer to software-based weaknesses that allow attackers to compromise the integrity, availability, or confidentiality of a system through malicious code execution or logic exploitation.

Memory-Based Vulnerabilities Memory vulnerabilities occur when applications mismanage how data is stored in RAM, often leading to unauthorized code execution. - Buffer Overflow: This occurs when an application receives more data than its allocated memory buffer can hold, causing data to spill into adjacent memory addresses. Attackers use this to overwrite return addresses and point to malicious code. - Integer Overflow: An arithmetic operation results in a value too large for the defined integer type. This can lead to logic errors or facilitate buffer overflows if the value is used for memory allocation. - Memory Leak: An application fails to release memory after it is no longer needed. Over time, this consumes available RAM, leading to a denial of service (DoS) as the system slows or crashes. - Memory Injection: Attackers "inject" malicious code into a running process's memory space to manipulate the application's behavior without altering the underlying file on disk.

Race Conditions and Logic Errors Concurrency and timing issues can be exploited when an application does not handle simultaneous events correctly. - Race Condition: A vulnerability where the system's behavior is dependent on the sequence or timing of uncontrollable events. If two threads access the same resource, an attacker may intervene between "check" and "use." - Time-of-Check to Time-of-Use (TOCTOU): A specific race condition where a file or variable is modified between the time the security credentials are verified and the time the resource is actually used. - Improper Error Handling: Applications that provide verbose error messages (like stack traces or database schemas) reveal internal configurations to attackers, aiding in reconnaissance. - Insecure Default Settings: Applications shipped with "out-of-the-box" configurations (e.g., admin/admin credentials) are easily exploited unless hardened by the administrator.

Vulnerability Management and Research Securing applications requires proactive identification of weaknesses through various intelligence sources. - Vendor Documentation: The primary source for patches, hardening guides, and known bug lists. - Vulnerability Feeds: Automated RSS or social media updates from organizations like the National Vulnerability Database (NVD) or CVE (Common Vulnerabilities and Exposures) lists. - Research Sources: Academic journals, industry conferences (e.g., Black Hat), and RFCs (Requests for Comments).

Quick recall - Buffer Overflow: Overwriting the "stack" to run unauthorized commands. - Memory Leak: Depletes system resources (RAM) causing a crash. - Race Condition: Exploits the gap in time between a security check and the action. - Legacy Systems: "Older versions" (e.g., Windows 7) that no longer receive security updates. - Pointer/Object Deference: Memory errors where an application follows a null or invalid pointer, leading to crashes.