HTTP Request Smuggling

Next is vulnerable to HTTP Request Smuggling. The vulnerability is due to inconsistent interpretation of a HTTP request, resulting in treating it as both a single request and two separate requests, leading to desynchronized responses. This allows attackers to craft HTTP request to manipulate or poison the response data seen by other users, potentially leading to unauthorized access or disclosure of sensitive information. This vulnerability is only exploitable if a route utilizes the rewrites feature.