Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown Firewall (a7c534abf) #691

Closed
WhatWaf-Firewalls opened this issue Jan 27, 2020 · 0 comments
Closed

Unknown Firewall (a7c534abf) #691

WhatWaf-Firewalls opened this issue Jan 27, 2020 · 0 comments

Comments

@WhatWaf-Firewalls
Copy link
Collaborator

WhatWaf version: 1.9.7
Running context: ./whatwaf -u ************************
Fingerprint:

<!--
GET http://online.gndu.ac.in HTTP/1.1
Status code: 400
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-Powered-By-Plesk: PleskWin
Date: Mon, 27 Jan 2020 06:55:25 GMT
Connection: close
Content-Length: 3802
-->
<!DOCTYPE html>

<html>
<head>
<title>A potentially dangerous Request.Path value was detected from the client (&lt;).</title>
<meta content="width=device-width" name="viewport"/>
<style>
         body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} 
         p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
         b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
         H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
         H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
         pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt}
         .marker {font-weight: bold; color: black;text-decoration: none;}
         .version {color: gray;}
         .error {margin-bottom: 10px;}
         .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
         @media screen and (max-width: 639px) {
          pre { width: 440px; overflow: auto; white-space: pre-wrap; word-wrap: break-word; }
         }
         @media screen and (max-width: 479px) {
          pre { width: 280px; }
         }
        </style>
</head>
<body bgcolor="white">
<span><h1>Server Error in '/' Application.<hr color="silver" size="1" width="100%"/></h1>
<h2> <i>A potentially dangerous Request.Path value was detected from the client (&lt;).</i> </h2></span>
<font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif ">
<b> Description: </b>An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

            <br/><br/>
<b> Exception Details: </b>System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (&lt;).<br/><br/>
<b>Source Error:</b> <br/><br/>
<table bgcolor="#ffffcc" width="100%">
<tr>
<td>
<code>

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.</code>
</td>
</tr>
</table>
<br/>
<b>Stack Trace:</b> <br/><br/>
<table bgcolor="#ffffcc" width="100%">
<tr>
<td>
<code><pre>

[HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (&lt;).]
   System.Web.HttpRequest.ValidateInputIfRequiredByConfig() +9939856
   System.Web.PipelineStepManager.ValidateHelper(HttpContext context) +53
</pre></code>
</td>
</tr>
</table>
<br/>
<hr color="silver" size="1" width="100%"/>
<b>Version Information:</b> Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3163.0

            </font>
</body>
</html>
<!-- 
[HttpException]: A potentially dangerous Request.Path value was detected from the client (&lt;).
   at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
   at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)
--><!-- 
This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using &lt;customErrors mode="Off"/&gt;. Consider using &lt;customErrors mode="On"/&gt; or &lt;customErrors mode="RemoteOnly"/&gt; in production environments.-->
@Ekultek Ekultek closed this as completed Feb 1, 2020
Ekultek pushed a commit that referenced this issue Feb 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants