Bug 6699 - XSS vulnerability in Mono's ASP.NET implementation.
Summary: XSS vulnerability in Mono's ASP.NET implementation.
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web (show other bugs)
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-08-27 06:40 UTC by filip
Modified: 2012-08-27 06:40 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 6699 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description filip 2012-08-27 06:40:29 UTC
I'm currently using 2.10.x on a Debian server. 
I'm running an ASP.NET MVC 3 application. 

It seems that when I query http://www.myserver.com/NONEXISTANTURL, without any custom error pages configured, I get the standard "Server Error in '/' Application" page saying "The resource cannot be found". The offending URL is repeated on the page, but without sanitizing it first.

The result is that when I query http://www.myserver.com/<h1>HELLO</h1> the HTML is included verbatim. I'm sure someone with more time can cause interesting XSS problems this way.

I've tried it on a few Mono sites that I know in production. Works on all of those who don't have a custom error page set up.