On a shared municipal app server, a process checks a file’s permissions, then an attacker replaces the file before it is used, gaining unauthorized access. Which vulnerability does this describe?
Select an answer to reveal the explanation.
Short Explanation
Check the lock, swap the door, then walk through — that timing gap is a TOC/TOU race condition. It is a concurrency bug, not a CIO phone scam or default RDP password. Shared municipal app servers need atomic permission checks and safe file-handling patterns.
Full Explanation
Time-of-check to time-of-use (TOC/TOU) race conditions occur when a security decision is made, then the underlying object changes before use. Objective 2.3 lists race conditions as a vulnerability type. Vishing, image-based delivery, and default credentials are different vectors. Shared app servers should use atomic operations, proper locking, and avoid TOCTOU-prone patterns for privilege checks.