Escape quotes in filename in ContentDisposition.Builder when charset not specified
See original GitHub issueThe filename, when specified without a charset, is quoted but not checked for the presence of any unquoted "
characters. We should check for those and turn into a quoted-pair.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to set 'Content-Disposition' and 'Filename' when using ...
I believe it deals with the file name sanitization. ContentDisposition contentDisposition = ContentDisposition.builder("inline") .filename("Filename") ...
Read more >ContentDisposition.Builder (Spring Framework 6.0.0 API)
Set the value of the filename parameter. The given filename will be formatted as quoted-string, as defined in RFC 2616, section 2.2, and...
Read more >RFC 6266 - Use of the Content-Disposition Header Field in ...
RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes...
Read more >HTTP headers and non-asci characters (Content-Disposition ...
The downloaded file name is specified by a filename parametr of Content-Disposition http header. There is no problem if you set only ASCII...
Read more >cfcontent - Adobe Support
To set the character encoding (character set) of generated output, ... file specified by the cfcontent tag using the filename specified by ...
Read more >
Top Related Medium Post
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@RockyMM it’s worth pointing out that versions prior to 5.0 were never affected by CVE-2020-5398 and that is why they are not listed in the CVE report.
The affected
ContentDisposition
type which can be used for the “inline” and “attachment” types that a server can use to suggest a file name to a client did not exist prior to version 5.0. There were however methods for “Content-Disposition” inHttpHeaders
but those are for “form-data” which is used to post data from a client to a server and hence a very different scenario. The change in #24580 was merely a minor improvement aimed at making the code consistent.To all affected in 4.3.x, this was solved by #24580 in 4.3.27. Security researchers (not Pivotal), please update the CVE report. 🙏