A user browses a website and clicks on a link which doesn’t seem to work, he is later accused of downloading the whole website.
-
Man in the middle attack.
-
Persistent Cross-site Scripting.
-
Phishing.
-
Log Injection.
Log injection involves inserting malicious entries into log files. A non-working link could be crafted to add fake entries (like 'downloaded whole website') to server logs, framing the user. MITM attacks intercept traffic, persistent XSS stores malicious scripts, phishing tricks users, and the scenario specifically mentions being accused based on logs.
Log Injection is an attack where unsanitized attacker-controlled input is written into application/server logs so fabricated entries appear in the audit trail. A classic abuse is framing an innocent user: an attacker plants a link that, when the victim clicks it (visibly "doesn't seem to work" - nothing happens on their screen), triggers a background request whose parameters get logged verbatim, forging entries that make it look like the victim's session bulk-downloaded the entire site. Later, log review 'proves' the user did this, even though nothing visible occurred for them. The other options don't fit: MITM requires intercepting/altering live traffic between two parties; persistent XSS needs a stored script executing for other visitors; phishing needs the user to be tricked into revealing credentials. None of those explain a user being falsely accused based on log evidence after an inert click - only Log Injection does.