Mar 30, 2024 07:34 AM
(This post was last modified: Mar 30, 2024 07:39 AM by feelsunbreeze.)
I have a site which is not properly sanitizing the input and returns "XML error" on the website.
However if I craft a simple XML payload, it's detected as an unhandled exception of dangerous input by ASP NET.
I was able to finally bypass their Cloudflare WAF with this but now ASP NET issue is arising.
What should I be looking into? Messing around to craft a payload that bypasses it?
I know the version of ASP NET is very old but I have no idea where to look for vulnerabilities in that version that will allow me to deliver a proper payload.
Cheers!
i.imgur.com/ 5EoNiDC.png
However if I craft a simple XML payload, it's detected as an unhandled exception of dangerous input by ASP NET.
I was able to finally bypass their Cloudflare WAF with this but now ASP NET issue is arising.
What should I be looking into? Messing around to craft a payload that bypasses it?
I know the version of ASP NET is very old but I have no idea where to look for vulnerabilities in that version that will allow me to deliver a proper payload.
Cheers!
i.imgur.com/ 5EoNiDC.png