Ian Graham of Citrix Online reported that when multiple Location headers were present in a redirect response Mozilla behavior differed from other browsers: Mozilla would use the second Location header while Chrome and Internet Explorer would use the first. Two copies of this header with different values could be a symptom of a CRLF injection attack against a vulnerable server. Most commonly it is the Location header itself that is vulnerable to the response splitting and therefore the copy preferred by Mozilla is more likely to be the malicious one. It is possible, however, that the first copy was the injected one depending on the nature of the server vulnerability. The Mozilla browser engine has been changed to treat two copies of this header with different values as an error condition. The same has been done with the headers Content-Length and Content-Disposition References: http://www.mozilla.org/security/announce/2011/mfsa2011-39.html https://bugzilla.mozilla.org/show_bug.cgi?id=655389
This issue has been addressed in following products: Red Hat Enterprise Linux 6 Via RHSA-2011:1342 https://rhn.redhat.com/errata/RHSA-2011-1342.html
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 6 Via RHSA-2011:1341 https://rhn.redhat.com/errata/RHSA-2011-1341.html