Has anyone encountered this issue. I am using my server in a government building when I did a security scan on this server the scan software (nCircle IP 360) found the problem below:
Versions of Apache webserver shipping with Red Hat Linux 7.0, (and possibly other Apache distributions) install with a default misconfiguration which can permit remote users to determine whether a given username exists on the vulnerable system.
When a remote user submits an HTTP request for a possible user's default home page, the server has one of three responses.
In a case where the tested username is valid, and that account has been configured with a homepage, the server replies with HTTP result code 200, and the user's homepage.
Alternatively, when the tested username does exist on the system, but does not have a homepage, the server responds with HTTP result code 403, and the server message "You don't have permission to access /~username on this server."
However, if the tested username does not exist as an account on the system, the Apache server's response is HTTP result code 404 and the message "The requested URL /~username was not found on this server."
Because the server responds differently in the latter two cases, a remote user can test and enumerate possible usernames. Properly exploited, this information could be used in further attacks on the vulnerable host.
SOLUTION
Workaround 1:
Disable the default-enabled UserDir directive:
% echo 'UserDir Disabled' >> /var/www/conf/httpd.conf
Workaround 2:
Substitute URL for pathname in httpd.conf:
% echo 'ErrorDocument 404
http://localhost/sample.html' >> /var/www/conf/httpd.conf
% echo 'ErrorDocument 403
http://localhost/sample.html' >> /var/www/conf/httpd.conf
% sudo apachectl restart
My server does give back the pages above if you manualy browse to the server.
Just wondering if I can use the fix above or if someone else here has a fix idea! Thanks guys!
3 Replies
1087 Views