If it's similar to a vulnerability reported a couple of years back, the gist of it would be. Some load balancers fronting multiple application connection throu

If it's similar to a vulnerability reported a couple of years back, the gist of it would be. Some load balancers fronting multiple application connection through multiplexed requests on a single HTTP 1.1 connection, and bugs occur with the handling (generally handling request boundaries). For example you can have a HTTP 1.1 front connection that behind the scenes operates a separate HTTP 1.0, 1.1, 2 or 3 connection. When smuggling additional data through the request you trip up the handler at the load balancer handler to inject a response that shouldn't be there, which will be served for one of the clients (even the wrong client request). Similar to HTTP response splitting attacks of the past. Eg. 3 requests come into the load balancer, and request 2 smuggles in an extra response that could be served as a response to request 1 or 3. That's how I understood the last such attack.