Does MS Anti-XSS block: HTTP Splitting and Cache Poisoning?

Does Microsoft's Anti-XSS Library block:

HTTP Splitting and Cache Poisoning?

These are new concepts to me, so surely I need to spend more time reading this article:

http://chousensha.github.io/blog/2014/08/15/pentest-lab-webgoat/

If you have the time... :)

Which vulnerability is NOT blocked by Microsoft's Anti-XSS Library?

Thanks
newbiewebSr. Software EngineerAsked:
Who is Participating?
 
Dr. KlahnPrincipal Software EngineerCommented:
https://www.owasp.org/index.php/Cache_Poisoning

A Cache Poisoning attack is possible because of HTTP Response Splitting and flaws in the web application.

https://www.owasp.org/index.php/HTTP_Response_Splitting

HTTP response splitting occurs when:

    Data enters a web application through an untrusted source, most frequently an HTTP request.
    The data is included in an HTTP response header sent to a web user without being validated for malicious characters.

So cross-site scripting protection will have no effect on either of these issues.
0
 
newbiewebSr. Software EngineerAuthor Commented:
So, I gather that these can not be stopped using:

1) the Anti-XSS library
2) enforcing URL whitelisting to block malicious URL's

I thought if I blocked the Return key it could stop Http splitting. No?

How do you block  Http splitting?
0
 
Dr. KlahnPrincipal Software EngineerCommented:
How do you block  Http splitting?

It would probably be best to close this question and ask that one in another question.  Then the experts in that area will see the title and can comment on it.  It's not an area I address on my site; but then, I don't run commerce on my site either.
0
 
newbiewebSr. Software EngineerAuthor Commented:
thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.