A transit download response places an unsanitized user-controlled filename into Content-Disposition and related headers. What issue class should the tester emphasize?
Select an answer to reveal the explanation.
Short Explanation
Stuffing raw user text into HTTP headers is like writing graffiti on the shipping label — parsers get confused. Filenames in Content-Disposition need sanitizing or the response can split, cache weirdly, or trigger script-ish download themes. Keep the finding on safe header handling.
Full Explanation
Reflecting untrusted data into response headers such as Content-Disposition can produce HTTP response splitting, cache poisoning, or scriptable download/filename issues depending on browser and encoding. Applications should sanitize or encode filenames and avoid CR/LF and special characters in headers. Testers describe the class and impact path without crafting weaponized header chains as the answer. HSTS preload status does not address this input-to-header flaw.