View source for SCG WS Apache

{{Template:OWASP Secure Configuration Guide}}

== Summary ==
The Apache HTTP Server Project is a collaborative software development effort aimed at creating a robust, commercial-grade, featureful, and freely-available source code implementation of an HTTP (Web) server. The project is jointly managed by a group of volunteers located around the world, using the Internet and the Web to communicate, plan, and develop the server and its related documentation. This project is part of the Apache Software Foundation. In addition, hundreds of users have contributed ideas, code, and documentation to the project. This file is intended to briefly describe the history of the Apache HTTP Server and recognize the many contributors.


== Common Misconfigurations ==

=== Misconfiguration 1 ===
==== Description ====

%ProductName% allows unauthorized attacker to list all users of the system ...

// Detailed description of the impact. Is it enabled by default? Vulnerable versions.

==== How to test ====

In order to test for %Misconfiguration_1%, one should ...

// Proof-of-concept here. Please include the screenshots and widely known tools/scanners!

==== Remediation ====

Initial/common value of parameter "listUsers" from config.xml is set to "true".

To assess the vulnerability it is enough to change the value to false: 

<pre>
<security>
	<listUsers>false</listUsers>
</security>
</pre>


== Misconfigurations ==

'''Server-status'''
Common misconfiguration is to have server-status enabled.
When navigating to website's url/server-status
an html page showing all ip's connected to server and software running on the server is shown.
This can be very embarrassing, and can be dangerous for people running websites using tor hidden services, because it will reveal their IP address.

Read more about it here:
*[http://httpd.apache.org/docs/2.2/mod/mod_status.html Mod Status Apache]
*[http://blog.sucuri.net/2012/10/popular-sites-with-apache-server-status-enabled.html Blog Post on server Status showing some sites with server-status enabled]

1. Version details disclosed in headers
disable apache tokens


2. Proper SSL cipher selection
Cipher orders
Disable specific ciphers

3. Guidelines on how to store ssl private keys on server
stuff like not to store private keys on /var/www/

4. Detailing about various authentication types

basic, digest, X509, LDAP or others.

Detailing about authoentication types and which one to use in which situation.

== References ==

https://httpd.apache.org/docs/current/misc/security_tips.html

https://wiki.debian.org/Apache/Hardening