lack of escaping of filename in content-disposition FileAttachment()
is vulnerable to Reflect File Download
#1621
Labels
FileAttachment()
is vulnerable to Reflect File Download
#1621
Describe the bug
The filename parameter of the Context.FileAttachment function is not properly sanitized. A maliciously crafted filename can cause the Content-Disposition header to be sent with an unexpected filename value or otherwise modify the Content-Disposition header. For example, a filename of "setup.bat";x=.txt" will be sent as a file named "setup.bat". If the FileAttachment function is called with names provided by an untrusted source, this may permit an attacker to cause a file to be served with a name different than provided. Maliciously crafted attachment file name can modify the Content-Disposition header.
pull-request
forpatched
the vulnerable on #1620Content-Disposition: attachment; filename="malicious.sh";dummy=.txt"
CWE-494
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Tasks
Context.FileAttachment
function #1620The text was updated successfully, but these errors were encountered: