Improper handling of filenames in Content-Disposition HTTP header in github.com/gin-gonic/gin
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.9.1.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| github.com/gin-gonic/gin | >=1.3.1-0.20190301021747-ccb9e902956d <1.9.1 | 1.9.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket