Skip to main content

Preventing Banner Grabbing in Web Servers

After a lot of googling I found nothing significant...then a friend of mine Vaibhav actually helped me with his precious knowledge.
This is a quick reference for preventing Banner Grabbing:

For Apache Server:


Edit your httpd.conf file and make sure the following directives are present:

ServerSignature Off

ServerTokens Prod

Disabling the ServerSignature token instructs Apache to not print version information when an error page such as a “404-Not Found” is displayed. The ServerTokens directive, when set to Prod, instructs Apache to only display “Server: Apache” in the banner. If you do not want to display “Apache” in the Server tag but want to display fake in-formation such as “Server: Not-allowed,” you will need to

1. Download the Apache source code.

2. Edit the file httpd.h and change the value of the string “Apache” in the line

#define SERVER_BASEPRODUCT "Apache"

to something else:

#define SERVER_BASEPRODUCT "Not-allowed"

3. Recompile, reinstall, and restart Apache.

***************

A different approach for changing the name in a source file is to replace the ap_set_version( ) function, which is responsible for construction of the server name in the first place. For Apache 1, replace the existing function (in http_main.c) with one like the following, specifying whatever server name you wish:

Static void ap_set_version(void)

{

/* set the server name /

Ap_add_version_component(“Microsoft-IIS/6.0”);

/ do not allow other modules to add to it */

Version_locked++;

}

For Apache 2, replace the function ( defined in core.c):

Static void ap_set_version(apr_pool_t pconf)

{

/ set the server name /

ap_add_version_component (pconf, “Microsoft-IIS/6.0”);

/ do not allow other modules to add to it */

Version_locked++;

}

****************

Using third party module: mod_security

A different approach to changing the name of the serve is to use a thirde-party module, mod_security. For this approach to work, you must allow Apache to reveal its full identity, and then instruct mod_security to change the identity to something else. The following directives can be added to Apache configuration:

# Reveal full identity (standard Apache directive)

ServerTokens Full

# Replace the server name (mod_security directive)

SecServerSignature “Microsoft-IIS/6.0”

Apache modules are not allowed to change the name of the server completely, but mod_security works by finding where the name is kept in memory and overwriting the text directly. The ServerTokens directive must be set to Full to ensure the web server allocates a large enough space for the name, giving mod_security enough space to make its changes later.


Microsoft IIS4 and IIS5:

1. Stop the World Wide Web Publishing service, and then edit

%systemroot%/system32/inetstrv/w3svc.dll

2. You can use notepad to edit it, or get a free hex editor.

3. Change both instances of 'Microsoft IIS/4.0' or 'Microsoft IIS/5.0'

inside the file. Both instances are located almost next to each other.

4. Restart the World Wide Web Publishing service.

Here is the output to a GET / HTTP/1.0:

GET / HTTP/1.0

HTTP/1.1 200 OK

Server: web server>

Date: Sat, 07 Apr 2001 02:13:48 GMT

Connection: Keep-Alive

Content-Length: 1270

Content-Type: text/html

Set-Cookie: ASPSESSIONIDQQQQGVFK=MJMLILDDLINNBHMPJIBEJCGL; path=/

Cache-control: private






Comments

Chintan Dave said…
Dude.... You could have asked the library sitting besides you :D

I could have reduced hell a lot of your effort on googling :D
Anonymous said…
Thanks for the information Nilesh ..can you please provide the same for Jboss web server .
Anonymous said…
How to solve banner grabbing problem n IIS 7

Popular posts from this blog

Ardilla- New tool for finding SQL Injection and XSS

Three Researchers -- MIT's Adam Kiezun , Stanford's Philip Guo , and Syracuse University's Karthick Jayaraman -- has developed a new tool ' Ardilla ' that automatically finds and exploits SQL injection and cross-site scripting vulnerabilities in Web applications. It creates inputs that pinpoint bugs in Web applications and then generates SQL injection and XSS attacks. But for now Ardilla is for PHP -based Web app only. The researchers say Ardilla found 68 never-before found vulnerabilities in five different PHP applications using the tool -- 23 SQL injection and 45 XSS flaws. More information is awaited. For their attack generation techniques refer to their document at: http://www.cs.washington.edu/homes/mernst/pubs/create-attacks-tr054.pdf

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated. Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string. This can be used for the bypass. It works for many servers, specially php servers. T

Combining power of Fiddler with Burp

Both are pretty powerful tools when it comes to intercept and modify http communications. But at some point of time, they become even more powerful combo if tied with each other. They complement each other. In a recent pentest I came across a similar situation where in Burp was not able to intercept a specific kind of traffic and Fiddler came to rescue. The application was designed to upload video. The initial communication was straight forward, I mean logging into application, filling up the video details etc. And all these were easily captured by Burp except the point where you hit the Upload Video and it connects to a different server and surprisingly it was not captured by Burp, not sure why, even after repeated attempts. So, I fired Fiddler to see if the it sees this request. But it's a;ways to play with requests using Burp due to it's various functionalities like, Intruder, Repeaters etc. But it was necessary to capture this request in Burp. So the below steps can be