Other nomination
x-up-devcap-post-charset Header in ASP.NET to Bypass WAFs Again
When the User-Agent starts with UP, ASP.NET takes the request body charset from the non-standard x-up-devcap-post-charset header instead of the Content-Type charset directive. An attacker encodes a POST payload in an exotic codepage such as ibm500, so a WAF that only whitelists Content-Type charsets sees nothing while the application decodes the attack.
Record
- Researcher
- Soroush Dalili
- Date
In the archive
Tags
This page is the archive's own catalogue record. The research is the work of Soroush Dalili, first published at the original source. Preserved copies are kept so the citation survives its host.