Content Type Tampering
This can lead to unauthorized actions, such as bypassing file type validation, injecting malicious content, or compromising data integrity.
Validate and sanitize the Content-Type
header on the server side, implement proper file type validation, and enforce security policies that restrict content types to expected and safe values.
JSON to XML
We can check the behaviour on different Content-Type
formats. This could result in:
Triggering verbose erros.
Bypass flawed defences.
Leverage differences in processing logic (e.g. secure with JSON but flawed with XML).
We can easily do that using Burp's Content Type Converter extension (Figure 1).
The below example is based on the crAPI application.

Adding Content-Type in the Request
Try adding Content-Type: application/json
in the request and send a blank body. This might return a stack trace!
Last updated
Was this helpful?