mailing list archives
Apache byte range vulnerability script
From: "Gillman, Joel - SAINT CORPORATION" <gillmanj () SAINTCORPORATION COM>
Date: Mon, 19 Dec 2011 18:56:25 +0000
I'd like to contribute a fix related to the Apache byte range
vulnerability detection script at
The current script submits a range request of eleven individual
byte ranges, short and not overlapping, with the comment that eleven
is "one more than allowed". This method may detect one of the early
vulnerability work-around configurations, but I don't believe it
reliably detects the (fixed) Apache versions 2.2.20 or 2.2.21 --
first, because I've found no mention of a limit of ten ranges in
connection with the Apache 2.2.20 or .21 releases, and second,
because a simple test against a running Apache 2.2.20 server did
not show that behavior.
Instead, I would suggest this change:
This requests more content than is present at the original URL,
regardless of the length of that content, and so should trigger
consolidation of three ranges (with response code 206) into
one range of the entire URL contents (with response code 200).
Apache's (subtle) reference to this behavior is in section "Caveats"
of http://httpd.apache.org/security/CVE-2011-3192.txt .
I hope this contribution is useful. :)
Security software developer
Saint Corporation http://www.saintcorporation.com
Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/
- Apache byte range vulnerability script Gillman, Joel - SAINT CORPORATION (Dec 19)