MonoX through 5.1.40.5152 allows remote code execution via HTML5Upload.ashx or Pages/SocialNetworking/lng/en-US/PhotoGallery.aspx because of deserialization in ModuleGallery.HTML5Upload, ModuleGallery.SilverLightUploadModule, HTML5Upload, and SilverLightUploadHandler.
MonoX through 5.1.40.5152 allows admins to execute arbitrary programs by reconfiguring the Converter Executable setting from ffmpeg.exe to a different program.
MonoX through 5.1.40.5152 allows administrators to execute arbitrary code by modifying an ASPX template.
Use-after-free vulnerability in Mono, when Moonlight 2.x before 2.4.1 or 3.x before 3.99.3 is used, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to finalizing and then resurrecting a DynamicMethod instance.
Race condition in the FastCopy optimization in the Array.Copy method in metadata/icall.c in Mono, when Moonlight 2.x before 2.4.1 or 3.x before 3.99.3 is used, allows remote attackers to trigger a buffer overflow and modify internal data structures, and cause a denial of service (plugin crash) or corrupt the internal state of the security manager, via a crafted media file in which a thread makes a change after a type check but before a copy action.
It was reported [1] that threads in Mono were not properly cleaned up upon finalization, so if one thread was resurrected, it would be possible to see the pointer to freed memory. This could lead to unintended information disclosure, and possibly a crash.
This has been corrected upstream [2].
[1] https://bugzilla.novell.com/showbug.cgi?id=678515 [2] https://github.com/mono/mono/commit/722f9890f09aadfc37ae479e7d946d5fc5ef7b91
Use-after-free vulnerability in Mono, when Moonlight 2.x before 2.4.1 or 3.x before 3.99.3 is used, allows remote attackers to cause a denial of service (plugin crash) or obtain sensitive information via vectors related to member data in a resurrected MonoThread instance.
MonoX through 5.1.40.5152 allows stored XSS via User Status, Blog Comments, or Blog Description.
StaticFileHandler.cs in System.Web in Mono before 1.2.5.2, when running on Windows, allows remote attackers to obtain source code of sensitive files via a request containing a trailing (1) space or (2) dot, which is not properly handled by XSP.
CRLF injection vulnerability in Sys.Web in Mono 2.0 and earlier allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the query string.
Multiple cross-site scripting (XSS) vulnerabilities in the ASP.net class libraries in Mono 2.0 and earlier allow remote attackers to inject arbitrary web script or HTML via crafted attributes related to (1) HtmlControl.cs (PreProcessRelativeReference), (2) HtmlForm.cs (RenderAttributes), (3) HtmlInputButton (RenderAttributes), (4) HtmlInputRadioButton (RenderAttributes), and (5) HtmlSelect (RenderChildren).
It was reported [1] that threads in Mono were not properly cleaned up upon finalization, so if one thread was resurrected, it would be possible to see the pointer to freed memory. This could lead to unintended information disclosure, and possibly a crash.
This has been corrected upstream [2].
[1] https://bugzilla.novell.com/showbug.cgi?id=678515 [2] https://github.com/mono/mono/commit/722f9890f09aadfc37ae479e7d946d5fc5ef7b91