This vulnerability leads to overwriting links to dynamic memory allocation (dynamic object pointers), heap headers, heap-based data, virtual function tables, etc. Attackers use this to take control of the program's execution.

This vulnerability leads to overwriting links to dynamic memory allocation (dynamic object pointers), heap headers, heap-based data, virtual function tables, etc. Attackers use this to take control of the program's execution.

• A. Stack-based buffer overflow
• B. Spiking
• C. Heap-based overflow
• D. Overwriting the EIP register

Answer: (C)

This is describing a heap-based overflow. When data written into a dynamically allocated block spills over the block’s boundaries, it can corrupt the heap’s management structures (like headers and free lists) and any data adjacent to that block. Attackers exploit this by overwriting pointers stored in the heap, such as dynamic object pointers or a virtual function table pointer in a C++ object. By corrupting these pointers, the program may end up executing attacker-controlled code, taking control of its execution. This differs from a stack-based overflow, which targets memory on the call stack and can overwrite the return address (often labeled EIP on x86). The scenario here centers on heap-allocated memory and objects, not the stack. Spiking isn’t the standard term for this vulnerability.

This is describing a heap-based overflow. When data written into a dynamically allocated block spills over the block’s boundaries, it can corrupt the heap’s management structures (like headers and free lists) and any data adjacent to that block. Attackers exploit this by overwriting pointers stored in the heap, such as dynamic object pointers or a virtual function table pointer in a C++ object. By corrupting these pointers, the program may end up executing attacker-controlled code, taking control of its execution.

This differs from a stack-based overflow, which targets memory on the call stack and can overwrite the return address (often labeled EIP on x86). The scenario here centers on heap-allocated memory and objects, not the stack. Spiking isn’t the standard term for this vulnerability.