Differences between revisions 2 and 3
Revision 2 as of 2007-11-28 21:10:33
Size: 3737
Editor: nat-pool-str
Comment: added code tags where needed
Revision 3 as of 2008-03-06 21:55:29
Size: 4355
Editor: markt
Comment: Add question list to start.
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Tomcat's security record is impeccable. There have been no public cases of damage done to a company, organization, or individual due to a Tomcat security issue. There have been no documented cases of data loss or application crashes caused by an intruder. While there have been numerous analyses conducted on Tomcat, partially because this is easy to do with Tomcat's source code openly available, there have been only a few '''theoretical''' vulnerabilities found. All of those were addressed rapidly even though there were no documented cases of actual exploitation of these vulnerabilities. There have been no public cases of damage done to a company, organization, or individual due to a Tomcat security issue. There have been no documented cases of data loss or application crashes caused by an intruder. While there have been numerous analyses conducted on Tomcat, partially because this is easy to do with Tomcat's source code openly available, there have been only '''theoretical''' vulnerabilities found. All of those were addressed even though there were no documented cases of actual exploitation of these vulnerabilities.
Line 11: Line 11:
 1. [#Q1 How do I use OpenSSL to set up my own Certificate Authority (CA)?]
 1. [#Q2 OH NO! PORT 8005 is available for anyone on localhost to shutdown my tomcat!]
 1. [#Q3 What about Tomcat running as root?]
 1. [#Q4 How to I force all my pages to run under HTTPS?]
 1. [#Q5 What is the default login for the manager and admin app?]
 1. [#Q6 How do I restrict access by ip address or remote host?]
 1. [#Q7 How do I use jsvc/procrun to run Tomcat on port 80 securely?]
 1. [#Q8 Has Tomcat's security been independently analyzed or audited?]
== Answers ==
Line 12: Line 21:
'''How do I use OpenSSL to set up my own Certificate Authority (CA)?''' [[Anchor(Q1)]]'''How do I use OpenSSL to set up my own Certificate Authority (CA)?'''
Line 16: Line 25:
'''OH NO! PORT 8005 is available for anyone on localhost to shutdown my tomcat!''' [[Anchor(Q2)]]'''OH NO! PORT 8005 is available for anyone on localhost to shutdown my tomcat!'''
Line 23: Line 32:
'''What about Tomcat running as root?''' [[Anchor(Q3)]]'''What about Tomcat running as root?'''
Line 29: Line 38:
''' How to I force all my pages to run under HTTPS?''' [[Anchor(Q4)]]'''How to I force all my pages to run under HTTPS?'''
Line 33: Line 42:
''' What is the default login for the manager and admin app?''' [[Anchor(Q5)]]'''What is the default login for the manager and admin app?'''
Line 37: Line 46:
''' How do I restrict access by ip address or remote host?''' [[Anchor(Q6)]]'''How do I restrict access by ip address or remote host?'''
Line 41: Line 50:
'''How do I use jsvc/procrun to run Tomcat on port 80 securely?''' [[Anchor(Q7)]]'''How do I use jsvc/procrun to run Tomcat on port 80 securely?'''
Line 45: Line 54:
''' Has Tomcat's security been independently analyzed or audited?''' [[Anchor(Q8)]]'''Has Tomcat's security been independently analyzed or audited?'''

Preface

This FAQ section provides help with some security-related issues. If you hear of a vulnerability or its exploitation, please let us know on the [mailto:security@tomcat.apache.org security@tomcat.apache.org] mailing list.

The Record

There have been no public cases of damage done to a company, organization, or individual due to a Tomcat security issue. There have been no documented cases of data loss or application crashes caused by an intruder. While there have been numerous analyses conducted on Tomcat, partially because this is easy to do with Tomcat's source code openly available, there have been only theoretical vulnerabilities found. All of those were addressed even though there were no documented cases of actual exploitation of these vulnerabilities.

Role of Customization

We believe, and the evidence suggests, that Tomcat is more than secure enough for most use-cases. However, like all other components of Tomcat, you can customize any and all of the relevant parts of the server to achieve even higher security. For example, the session manager implementation is pluggable, and even the default implementation has support for pluggable random number generators. If you have a special need that you feel is not met by Tomcat out of the box, consider these customization options. At the same time, please bring up your requirements on the user mailing list, where we'll be glad to discuss it and assist in your approach/design/implementation as needed.

Questions

  1. [#Q1 How do I use OpenSSL to set up my own Certificate Authority (CA)?]
  2. [#Q2 OH NO! PORT 8005 is available for anyone on localhost to shutdown my tomcat!]
  3. [#Q3 What about Tomcat running as root?]
  4. [#Q4 How to I force all my pages to run under HTTPS?]
  5. [#Q5 What is the default login for the manager and admin app?]
  6. [#Q6 How do I restrict access by ip address or remote host?]
  7. [#Q7 How do I use jsvc/procrun to run Tomcat on port 80 securely?]
  8. [#Q8 Has Tomcat's security been independently analyzed or audited?]

Answers

Anchor(Q1)How do I use OpenSSL to set up my own Certificate Authority (CA)?

[http://marc.theaimsgroup.com/?l=tomcat-user&m=106293430225790&w=2 Using OpenSSL to set up your own CA].

Anchor(Q2)OH NO! PORT 8005 is available for anyone on localhost to shutdown my tomcat!

See these 2 discussions.

Anchor(Q3)What about Tomcat running as root?

See these threads:

Anchor(Q4)How to I force all my pages to run under HTTPS?

[http://marc.theaimsgroup.com/?l=tomcat-user&m=104951559722619&w=2 Use security-constraint in web.xml].

Anchor(Q5)What is the default login for the manager and admin app?

The admin and manager application do not provide a default login. Doing so is a security flaw. You need to edit $CATALINA_HOME/conf/tomcat-users.xml if you are using the default install. [http://tomcat.apache.org/tomcat-4.1-doc/manager-howto.html#Configuring%20Manager%20Application%20Access Configuring Manager Application Access]

Anchor(Q6)How do I restrict access by ip address or remote host?

By using the RemoteHostValve or RemoteAddrValve. Warning, these valves rely on accurate incoming ip addresses or hostnames. So they can fall victim to spoofing! [http://tomcat.apache.org/tomcat-4.1-doc/config/valve.html Valve Reference Link]

Anchor(Q7)How do I use jsvc/procrun to run Tomcat on port 80 securely?

Fairly easily ;) See the Setup page in the docs for your tomcat release, and read [http://marc.theaimsgroup.com/?l=tomcat-user&m=108566020231438&w=2 this mailing list post] for a complete setup example with permissions etc.

Anchor(Q8)Has Tomcat's security been independently analyzed or audited?

Yes, by numerous organizations and individuals, many times. Try [http://www.google.com/search?sourceid=navclient&ie=UTF-8&q=is+tomcat+secure this Google search] and you'll see many references, guides, and analyses.

FAQ/Security (last edited 2015-03-06 09:18:59 by markt)