A legacy document-scanning service crashes when fed an oversized input, and analysis shows adjacent memory was overwritten before a suspicious process started. Which application vulnerability class best fits?
Select an answer to reveal the explanation.
Short Explanation
Too much data shoved into too small a memory bucket is a buffer overflow — classic application memory-safety failure. Social lies and guest Wi-Fi bridging are different problems. Replace or harden that legacy scanner service before someone turns the crash into code execution.
Full Explanation
Buffer overflows are application vulnerabilities where input exceeds a buffer and corrupts memory, potentially enabling crashes or code execution. Objective 2.3 lists buffer overflow under application vulnerability types. Misinformation, unsecure wireless, and BEC are threat vectors, not this memory-safety class. Municipal legacy services should be patched, isolated, or rewritten with safer languages and input bounds checking.