HawkScan Test Info for Trace.axd Information Leak

Trace.axd Information Leak


Plugin Id: 40029 | CWE: 215


To remediate the Trace.axd Information Leak vulnerability, follow these steps:

  1. Disable trace.axd: The trace.axd component should be disabled in the ASP.NET application to prevent the leakage of sensitive information. This can be done by adding the following configuration to the web.config file:

      <trace enabled="false" />

    This configuration will disable the trace.axd component and prevent any information leakage.

  2. Implement proper access controls: Ensure that access to the trace.axd component is restricted to authorized users only. This can be done by adding the following configuration to the web.config file:

    <location path="trace.axd">
          <deny users="?" />
          <allow roles="Administrators" />
          <deny users="*" />

    This configuration will deny access to anonymous users, allow access to users in the “Administrators” role, and deny access to all other users.

  3. Regularly update and patch: Keep the ASP.NET framework and all related components up to date with the latest patches and updates. This will help to mitigate any known vulnerabilities, including the Trace.axd Information Leak.


The ASP.NET Trace Viewer (trace.axd) is a component that provides detailed tracing and debugging information about an ASP.NET application. It can be accessed by appending “/trace.axd” to the application’s URL. However, if not properly secured, this component can leak a significant amount of valuable information, including sensitive data, server configuration details, and potentially even source code.


The Trace.axd Information Leak vulnerability poses several risks to an ASP.NET application:

  1. Information disclosure: The trace.axd component can leak sensitive information, such as database connection strings, session IDs, and other application-specific data. This information can be exploited by attackers to gain unauthorized access or perform other malicious activities.

  2. Server configuration exposure: The trace.axd component can reveal detailed server configuration information, including the version of ASP.NET, installed modules, and other system details. This information can be used by attackers to identify vulnerabilities and plan targeted attacks.

  3. Source code exposure: In some cases, the trace.axd component may inadvertently expose source code files, allowing attackers to view and potentially exploit application logic or discover additional vulnerabilities.

It is crucial to address this vulnerability promptly to prevent the leakage of sensitive information and protect the security of the ASP.NET application.