Which action prevents buffer overflow attacks?

The correct answer is C. input sanitization. Buffer Overflow Attack Prevention Input sanitization (C) directly prevents buffer overflow attacks by validating, filtering, and enforcing length limits on user-supplied data before it is processed - this ensures malicious input cannot exceed allocated memory boundaries and…

Submitted by ricky.ec· Mar 6, 2026Security Concepts

Question

Options

Avariable randomization
Busing web based applications
Cinput sanitization
Dusing a Linux operating system

How the community answered

(42 responses)

A
2% (1)
B
7% (3)
C
88% (37)
D
2% (1)

Explanation

Buffer Overflow Attack Prevention

Input sanitization (C) directly prevents buffer overflow attacks by validating, filtering, and enforcing length limits on user-supplied data before it is processed - this ensures malicious input cannot exceed allocated memory boundaries and overwrite adjacent memory locations.

Variable randomization (A) refers to Address Space Layout Randomization (ASLR), which makes exploitation harder but does not prevent the overflow itself - it's a mitigation technique, not a prevention method. Web-based applications (B) are irrelevant and actually introduce their own vulnerabilities; the platform type doesn't inherently prevent buffer overflows. Linux (D) is equally misleading - buffer overflows exist across all operating systems, and no single OS eliminates the vulnerability.

Memory Tip: Think of input sanitization as a bouncer at the door - it checks every piece of data entering the system and rejects anything that's too large or malformed before it can cause damage inside the buffer.

Topics

#Buffer Overflow Prevention#Input Sanitization#Application Security#Vulnerability Management

Community Discussion

No community discussion yet for this question.

Full 200-201 Practice