We ran a vulerability assesment and here are 2 issues that popped up. Since Tomcat does not have an httpd.conf file, what options are needed to be set to fix these? Also, what's the option for creating custom 404/403 pages?
The Mac OS X Finder creates a file called .DS_Store in each directory that it views. Some versions of OS X include system configuration information and file location information in these files. The .DS_Store files can be accessed from this server via a web request such as Service: Apache-Coyote/1.1
Bugtraq:3316
Configure your Apache server to block access to these files with the FileMatch feature of httpd.conf.
Some distributions of Apache, especially in Red Hat 7.0, allow an attacker to probe a system for user names via requests for
user home pages (e.g., Service: Apache-Coyote/1.1
CVE:CAN-2001-1013
Bugtraq:3335
Disabling the UserDir directive in the Apache configuration file (httpd.conf) will prevent this, although it will also prevent users from providing their own web pages. Alternately, specify ErrorDocuments for both 403 (Forbidden) and 404 (Page Not Found) responses.
The Mac OS X Finder creates a file called .DS_Store in each directory that it views. Some versions of OS X include system configuration information and file location information in these files. The .DS_Store files can be accessed from this server via a web request such as Service: Apache-Coyote/1.1
Bugtraq:3316
Configure your Apache server to block access to these files with the FileMatch feature of httpd.conf.
Some distributions of Apache, especially in Red Hat 7.0, allow an attacker to probe a system for user names via requests for
user home pages (e.g., Service: Apache-Coyote/1.1
CVE:CAN-2001-1013
Bugtraq:3335
Disabling the UserDir directive in the Apache configuration file (httpd.conf) will prevent this, although it will also prevent users from providing their own web pages. Alternately, specify ErrorDocuments for both 403 (Forbidden) and 404 (Page Not Found) responses.