HTTP Server Response Header

HTTP Server Response Header is a vulnerability that can be exploited by attackers to gather information about the web server and the software it is running. It can also be used to identify the version of the web server software and the operating system it is running on, which can be used to launch targeted attacks against the web application. In this guide, we will provide a step-by-step process on how to fix this vulnerability.

‍

Step 1: Identify the Server Response Header

The first step in fixing this vulnerability is to identify the server response header. This header can be found in the HTTP response sent by the server when a request is made to the web application. The server response header typically includes information about the server, the software it is running, and the operating system it is running on.

To identify the server response header, you can use a tool like Burp Suite or OWASP ZAP. These tools allow you to intercept and analyze HTTP requests and responses. To intercept the HTTP response, you can use the following steps:

1. Launch Burp Suite or OWASP ZAP.
2. Configure your web browser to use the proxy provided by the tool.
3. Browse to the web application and perform an action that triggers a request.
4. Intercept the HTTP response using the tool.

Once you have intercepted the HTTP response, you can analyze the server response header to identify any sensitive information that is being disclosed.

‍

Step 2: Remove Sensitive Information from the Server Response Header

The second step in fixing this vulnerability is to remove any sensitive information from the server response header. This can be done by modifying the configuration of the web server software.

For example, if you are using Apache HTTP Server, you can modify the configuration file (httpd.conf) to remove sensitive information from the server response header. To do this, you can use the following steps:

1. Open the httpd.conf file using a text editor.
2. Locate the ServerTokens directive.
3. Set the value of the ServerTokens directive to "Prod" or "Minimal".
4. Save the changes to the httpd.conf file.
5. Restart the Apache HTTP Server.

The ServerTokens directive controls what information is included in the server response header. The "Prod" value removes all information about the server software and operating system, while the "Minimal" value only includes the server software name and version.

‍

Step 3: Add Custom Server Response Header

The third step in fixing this vulnerability is to add a custom server response header. This header can be used to provide additional information about the web application and the security measures that have been implemented.

To add a custom server response header, you can modify the configuration of the web server software. For example, if you are using Apache HTTP Server, you can modify the httpd.conf file to add a custom header. To do this, you can use the following steps:

1. Open the httpd.conf file using a text editor.
2. Locate the ServerTokens directive.

Add the following line below the ServerTokens directive:

3. Header always set Custom-Header "Custom Value"
4. Save the changes to the httpd.conf file.
5. Restart the Apache HTTP Server.

The "Header always set" directive is used to add a custom header to the server response. In this example, we are adding a custom header called "Custom-Header" with a value of "Custom Value". You can replace "Custom-Header" and "Custom Value" with your own custom values.

‍

Step 4: Verify the Changes

The final step in fixing this vulnerability is to verify that the changes have been applied successfully. To do this, you can use the same tool you used in Step 1 to intercept the HTTP response and check the server response header.

If the server response header no longer includes sensitive information and the custom header has been added successfully, then the vulnerability has been fixed. You should also perform additional testing to ensure that the web application is functioning correctly and that the changes have not introduced any new issues.

‍

Conclusion

HTTP Server Response Header is a vulnerability that can be exploited by attackers to gather information about the web server and the software it is running. In this guide, we provided a step-by-step process on how to fix this vulnerability by removing sensitive information from the server response header and adding a custom header. It is important to regularly scan and test your web application for vulnerabilities and apply security measures to protect against potential attacks.

‍