Repository navigation
suspicion of double encoding in referrer field - prob. false alarm #54
Description
From nada...@gmail.com on October 25, 2009 09:10:04
What steps will reproduce the problem? 1.Create a HTTP Request where the referrer field holds a URL with an
ampersand (&) for parameters. 2. 3. What is the expected output? What do you see instead? referrer field with amperstand should be legit.
Instead, ESAPI finds it as a double encoding hacking attach. What version of the product are you using? On what operating system? 1.4 on Unix Please provide any additional information below.
Original issue: http://code.google.com/p/owasp-esapi-java/issues/detail?id=44
Activity
meg23 commentedon Nov 13, 2014
From chrisisbeef on October 28, 2009 22:15:03
Need to check if this is still the case in 2.0 - If so it can be resolved there and
will vote on whether to release a patch to 1.4 to resolve the issue there.
Owner: chrisisbeef
Labels: Component-Logic
meg23 commentedon Nov 13, 2014
From chrisisbeef on December 01, 2009 23:29:56
Additional information here would be helpful. Can you include a code sample that
illustrates your issue?
meg23 commentedon Nov 13, 2014
From manico.james@gmail.com on October 31, 2010 23:00:39
We already addresses this in the latest enhancements to cannonicalization. I'm dropping this unless someone brings this up again.
Status: Fixed
meg23 commentedon Nov 13, 2014
From chrisisbeef on November 01, 2010 00:13:06
drop +1