- Author: email@example.com
- Copyright: Cyberis Limited 2013
- License: GPLv3 (See LICENSE)
A server-side PHP script to manipulate HTTP Response Headers, designed to identify weaknesses in perimeter filtering devices (e.g. web proxies and next generation firewalls). Also includes a low[er] level Perl script allowing you to manipulate the entire response (such as HTTP version etc) - httpversioncoder.pl.
ResponseCoder is designed to allow you to easily manipulate HTTP response headers - specifically to identify weaknesses in perimeter filtering appliances such as web proxies and next generation firewalls. It's an open source PHP script that formulates HTTP response headers on-the-fly, allowing the operator to form specific test cases as necessary.
The test cases are centred around the download of a Win32 executable - a common file format that is often blocked at the perimeter to prevent unauthorised code and malware from entering the corporate environment. To test the download of 'permissible' files, a text file can also be specified, allowing you to concentrate on discovering the oddities of any intermediary filtering devices.
Obviously manipulation of such HTTP response headers may lead to unexpected results in your browser - redirect codes, client errors and server error codes are typical examples that may (or should) cause a browser to ignore the body of a response. Try it for yourself - a 201 in Internet Explorer for example will cause it to ignore the specified filename in the 'Content-Disposition' header, whilst Chrome will accept that just fine.
There are numerous tests you can conduct with HTTP response headers (take a look over at http://greenbytes.de/tech/tc2231/ for some ideas), and this script certainly doesn't expose all possible scenarios. However it does provide a quick testing framework which is easier to use and more intuitive than NetCat.
An online version of the PHP script is accessible in our labs - http://labs.cyberis.co.uk/ResponseCoder/
- Ability to set common HTTP response headers
- Ability to encode numerous 'Content-Encoding' types, including gzip, deflate (both RFC1950 and RFC1951), bzip, compress, base64 and SDCH
- Multiple layers of encoding (responsecoder.php stacks up to 2 different types of encoding at once, with up to 10 rounds of gzip compression). If you want an arbitrary number of rounds of gzip encoded, test out gzipPoC.php
- Supports Chunked Transport-Encoding
Apache and PHP are required (other web servers that support PHP may work - but you'll need to check how the server handles tampering with response headers). It is recommended that you edit php.ini to remove any default 'Content-Type' header - set default_mimetype to null.
You'll also need to ensure you have a Unix compress tool (e.g ncompress) installed for 'compress' Content-Type encodings.
To test for SDCH filtering bypass issues, you'll need a compatible browser, namely Chrome. You'll also need to set up your server with a FQDN - Chrome doesn't seem to like plain host names or IP addresses when using SDCH.
If you want to dive even deeper, you'll need Perl and the following modules to use httpversioncoder.pl:
use Term::ANSIColor; use IO::Socket;
Kindly report all issues via https://github.com/cyberisltd/ResponseCoder/issues