Closed davidbernick closed 9 years ago
I do see that the logout mechanism creates an open redirect so it would be better to restrict the URLs by default to the domain the web server runs on (optionally tightened up further by a config option).
I don't see how the headers would poison the cache. Headers can be added from user agents regardless of the logout mechanism. Can you elaborate?
From what I understand (and I could be wrong), inserting headers can lead to these two kinds of attacks. I would call these "medium" attacks, not critical or show-stoppers. I don't think this is a bug or a really big deal, but it's something: https://www.owasp.org/index.php/HTTP_Response_Splitting https://www.owasp.org/index.php/Cache_Poisoning
ok, I did not inspect the request URL closely enough, I see what you mean now; all 3 attacks (open redirect, response splitting, cache poisoning) result from the fact that the value of the logout parameter in not validated, I will add that
please check this branch: https://github.com/pingidentity/mod_auth_openidc/commits/fix-logout-validation
in the master branch now since https://github.com/pingidentity/mod_auth_openidc/commit/15e936c484a44388dcd0ef3a478d6c6d8264feea
Hi all!
I was doing a scan (IBM AppScan to be precise) and
So if a user is successfully phished to click on a logout link (in an email or website or whatever) they could insert headers into the redirect which can poison the cache, right?
Is there a way to have a parameter sanitized somehow? A list of exact urls for redirection?