How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

346,350

Total vulnerabilities in the database

Vulnerabilities for products matching "tomcat"

Found 2 matching products. Filters apply to all results.

You can search for specific versions with /product/tomcat/1.2.3

apache / tomcat

8879 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2008-0128	Medium	January 23, 2008 1/23/08	<= 5.5.20
CVE-2007-5342	Medium	December 27, 2007 12/27/07	== 5.5.18 == 6.0.6 == 6.0.11 == 5.5.12 == 5.5.14 == 5.5.10 == 6.0.7 == 5.5.11 == 6.0.4 == 5.5.20 == 5.5.15 == 6.0.15 == 5.5.21 == 5.5.22 == 6.0.10 == 6.0.3 == 6.0.9 == 6.0 == 5.5.9 == 5.5.25 == 6.0.14 == 5.5.13 == 6.0.1 == 6.0.12 == 5.5.24 == 5.5.16 == 6.0.5 == 5.5.17 == 5.5.19 == 6.0.2 == 6.0.13 == 5.5.23 == 6.0.8
CVE-2007-5461	Low	October 15, 2007 10/15/07	== 4.1.2 == 4.0.4 == 4.1.35 == 4.1.36 == 4.1.21 == 4.1.24 == 4.1.25 == 4.1.4 == 4.1.27 == 4.1.30 == 4.1.7 == 4.1.11 == 4.1.18 == 4.1.14 == 4.1.19 == 4.1.31 == 4.1.16 == 4.1.29 == 4.1.22 == 4.0.6 == 4.1.5 == 4.1.26 == 4.1.13 == 4.1.8 == 4.0.3 == 4.1.17 == 4.0.1 == 4.1.33 == 4.1.1 == 4.1.12 == 4.1.28 == 4.1.15 == 4.1.10 == 4.1.0 == 4.1.20 == 4.0.2 == 4.1.3 == 4.0.5 == 4.1.23 == 4.0.0 == 4.1.34 == 4.1.32 == 4.1.6 == 4.1.9
CVE-2007-4724	Low	September 5, 2007 9/5/07	== 4.1.31
CVE-2007-3382	Low	August 14, 2007 8/14/07	== 4.1.2 == 4.1.36 == 4.1.9-beta == 5.5.18 == 5.0.8 == 5.0.19 == 6.0.6 == 6.0.11 == 5.5.12 == 5.0.14 == 5.5.14 == 4.1.24 == 5.5.10 == 5.0.22 == 5.5.4 == 5.5.7 == 5.5.1 == 5.0.7 == 6.0.7 == 5.5.11 == 6.0.4 == 5.5.6 == 5.0.9 == 5.0.15 == 3.3.2 == 5.0.30 == 5.5.20 == 5.5.15 == 5.0.23 == 5.0.2 == 5.5.5 == 5.0.10 == 5.0.21 == 5.0.26 == 5.5.21 == 5.5.22 == 6.0.10 == 6.0.3 == 5.0.0 == 5.0.6 == 6.0.9 == 4.1.31 == 5.5.3 == 5.0.27 == 5.0.16 == 5.5.9 == 5.0.18 == 6.0.0 == 3.3.1a == 5.5.2 == 5.0.5 == 5.0.28 == 5.0.29 == 5.5.0 == 4.1.1 == 5.5.13 == 6.0.1 == 6.0.12 == 5.5.24 == 4.1.28 == 5.0.13 == 4.1.15 == 4.1.3-beta == 4.1.10 == 5.5.8 == 5.0.17 == 5.5.16 == 4.1.0 == 6.0.5 == 5.5.17 == 4.1.3 == 5.5.19 == 5.0.4 == 6.0.2 == 5.0.25 == 6.0.13 == 5.0.1 == 3.3.1 == 5.0.11 == 5.5.23 == 5.0.3 == 5.0.24 == 3.3 == 6.0.8 == 5.0.12
CVE-2007-3385	Low	August 14, 2007 8/14/07	== 4.1.2 == 4.1.36 == 4.1.9-beta == 5.5.18 == 5.0.8 == 5.0.19 == 6.0.6 == 6.0.11 == 5.5.12 == 5.0.14 == 5.5.14 == 4.1.24 == 5.5.10 == 5.0.22 == 5.5.4 == 5.5.7 == 5.5.1 == 5.0.7 == 6.0.7 == 5.5.11 == 6.0.4 == 5.5.6 == 5.0.9 == 5.0.15 == 3.3.2 == 5.0.30 == 5.5.20 == 5.5.15 == 5.0.23 == 5.0.2 == 5.5.5 == 5.0.10 == 5.0.21 == 5.0.26 == 5.5.21 == 5.5.22 == 6.0.10 == 6.0.3 == 5.0.0 == 5.0.6 == 6.0.9 == 4.1.31 == 5.5.3 == 5.0.27 == 5.0.16 == 5.5.9 == 5.0.18 == 6.0.0 == 3.3.1a == 5.5.2 == 5.0.5 == 5.0.28 == 5.0.29 == 5.5.0 == 4.1.1 == 5.5.13 == 6.0.1 == 6.0.12 == 5.5.24 == 4.1.28 == 5.0.13 == 4.1.15 == 4.1.3-beta == 4.1.10 == 5.5.8 == 5.0.17 == 5.5.16 == 4.1.0 == 6.0.5 == 5.5.17 == 4.1.3 == 5.5.19 == 5.0.4 == 6.0.2 == 5.0.25 == 6.0.13 == 5.0.1 == 3.3.1 == 5.0.11 == 5.5.23 == 5.0.3 == 5.0.24 == 3.3 == 6.0.8 == 5.0.12
CVE-2007-3386	Low	August 14, 2007 8/14/07	== 5.5.18 == 6.0.6 == 6.0.11 == 5.5.12 == 5.5.14 == 5.5.10 == 5.5.4 == 5.5.7 == 5.5.1 == 6.0.7 == 5.5.11 == 6.0.4 == 5.5.6 == 5.5.20 == 5.5.15 == 5.5.5 == 5.5.21 == 5.5.22 == 6.0.10 == 6.0.3 == 6.0.9 == 5.5.3 == 5.5.9 == 6.0.0 == 5.5.2 == 5.5.0 == 5.5.13 == 6.0.1 == 6.0.12 == 5.5.24 == 5.5.8 == 5.5.16 == 6.0.5 == 5.5.17 == 5.5.19 == 6.0.2 == 6.0.13 == 5.5.23 == 6.0.8
CVE-2007-3384	Low	August 8, 2007 8/8/07	== 3.3.2 == 3.3.1a == 3.3.1 == 3.3
CVE-2007-3383	Low	July 25, 2007 7/25/07	== 4.1.2 == 4.0.4 == 4.1.36 == 4.1.24 == 4.1.31 == 4.0.6 == 4.0.3 == 4.0.1 == 4.1.1 == 4.1.28 == 4.1.15 == 4.1.10 == 4.1.0 == 4.0.2 == 4.1.3 == 4.0.5 == 4.0.0
CVE-2007-2449	Low	June 14, 2007 6/14/07	== 4.0.4 == 5.5.18 == 5.0.8 == 5.0.19 == 6.0.6 == 6.0.11 == 5.5.12 == 5.0.14 == 5.5.14 == 5.5.10 == 5.0.22 == 5.5.4 == 5.5.7 == 5.5.1 == 5.0.7 == 6.0.7 == 5.5.11 == 6.0.4 == 5.5.6 == 5.0.9 == 5.0.15 == 5.0.30 == 5.5.20 == 5.5.15 == 5.0.23 == 5.0.2 == 5.5.5 == 5.0.10 == 5.0.21 == 5.0.26 == 5.5.21 == 5.5.22 == 6.0.10 == 6.0.3 == 5.0.0 == 5.0.6 == 5.5.3 == 5.0.27 == 5.0.16 == 5.5.9 == 4.0.3 == 5.0.18 == 6.0.0 == 4.0.1 == 5.5.2 == 5.0.5 == 5.0.28 == 5.0.29 == 5.5.0 == 5.5.13 == 6.0.1 == 6.0.12 == 5.0.13 <= 4.1.36 == 5.5.8 == 5.0.17 == 5.5.16 == 6.0.5 == 4.0.2 == 5.5.17 == 5.5.19 == 4.0.5 == 4.0.0 == 5.0.4 == 6.0.2 == 5.0.25 == 6.0.13 == 5.0.1 == 5.0.11 == 5.0.3 == 5.0.24 == 6.0.8 == 5.0.12
CVE-2007-2450	Low	June 14, 2007 6/14/07	== 4.1.2 == 4.0.4 == 4.1.36 == 4.1.9-beta == 5.5.18 == 5.0.8 == 5.0.19 == 6.0.6 == 6.0.11 == 5.5.12 == 5.0.14 == 5.5.14 == 4.1.24 == 5.5.10 == 5.0.22 == 5.5.4 == 5.5.7 == 5.5.1 == 5.0.7 == 6.0.7 == 5.5.11 == 6.0.4 == 5.5.6 == 5.0.9 == 5.0.15 == 5.0.30 == 5.5.20 == 5.5.15 == 5.0.23 == 5.0.2 == 5.5.5 == 5.0.10 == 5.0.21 == 5.0.26 == 5.5.21 == 5.5.22 == 6.0.10 == 6.0.3 == 5.0.0 == 5.0.6 == 6.0.9 == 4.1.31 == 5.5.3 == 5.0.27 == 5.0.16 == 4.0.6 == 5.5.9 == 4.0.3 == 5.0.18 == 6.0.0 == 4.0.1 == 5.5.2 == 5.0.5 == 5.0.28 == 5.0.29 == 5.5.0 == 4.1.1 == 5.5.13 == 6.0.1 == 6.0.12 == 5.5.24 == 4.1.28 == 5.0.13 == 4.1.15 == 4.1.3-beta == 4.1.10 == 5.5.8 == 5.0.17 == 5.5.16 == 4.1.0 == 6.0.5 == 4.0.2 == 5.5.17 == 4.1.3 == 5.5.19 == 4.0.5 == 4.0.0 == 5.0.4 == 6.0.2 == 5.0.25 == 6.0.13 == 5.0.1 == 5.0.11 == 5.5.23 == 5.0.3 == 5.0.24 == 6.0.8 == 5.0.12
CVE-2007-1355	Low	May 21, 2007 5/21/07	== 4.0.4 == 5.0.8 == 5.0.19 == 6.0.6 == 5.0.14 == 4.1.24 == 5.0.22 == 5.0.7 == 6.0.7 == 6.0.4 == 5.0.9 == 5.0.15 == 5.0.30 == 5.0.23 == 5.0.2 == 5.0.10 == 5.0.21 == 5.0.26 == 6.0.10 == 6.0.3 == 5.0.6 == 6.0.9 == 4.1.31 == 5.0.27 == 5.0.16 == 4.0.6 == 4.0.3 == 5.0.18 == 6.0.0 == 4.0.1 == 5.0.5 == 5.0.28 == 5.0.29 == 6.0.1 == 4.1.28 == 5.0.13 == 4.1.15 == 4.1.10 == 5.0.17 == 6.0.5 == 4.0.2 == 4.0.5 == 4.0.0 == 5.0.4 == 6.0.2 == 5.0.25 == 5.0.1 == 5.0.11 == 5.0.3 == 5.0.24 == 6.0.8 == 5.0.12
CVE-2006-7195	Low	May 10, 2007 5/10/07	== 5.0.19 == 5.5.12 == 5.0.14 == 5.5.14 == 5.5.10 == 5.0.22 == 5.5.7 == 5.5.11 == 5.5.6 == 5.0.15 == 5.0.30 == 5.5.15 == 5.0.23 == 5.0.2 == 5.5.5 == 5.0.10 == 5.0.21 == 5.0.26 == 5.0.0 == 5.0.27 == 5.0.16 == 5.5.9 == 5.0.18 == 5.0.28 == 5.0.29 == 5.5.0 == 5.5.13 == 5.0.13 == 5.5.8 == 5.0.17 == 5.5.16 == 5.5.17 == 5.0.25 == 5.0.1 == 5.0.11 == 5.0.24 == 5.0.12
CVE-2006-7196	Low	May 10, 2007 5/10/07	== 4.0.4 == 5.0.8 == 5.0.19 == 5.5.12 == 5.0.14 == 5.5.14 == 5.5.10 == 5.0.22 == 5.5.4 == 5.5.7 == 5.5.1 == 5.0.7 == 5.5.11 == 5.5.6 == 5.0.9 == 5.0.15 == 5.0.30 == 5.5.15 == 5.0.23 == 5.0.2 == 5.5.5 == 5.0.10 == 5.0.21 == 5.0.26 == 5.0.0 == 5.0.6 == 5.5.3 == 5.0.27 == 5.0.16 == 4.0.6 == 5.5.9 == 4.0.3 == 5.0.18 == 4.0.1 == 5.5.2 == 5.0.5 == 5.0.28 == 5.0.29 == 5.5.0 == 5.5.13 == 5.0.13 == 5.5.8 == 5.0.17 == 4.0.2 == 4.0.5 == 4.0.0 == 5.0.4 == 5.0.25 == 5.0.1 == 5.0.11 == 5.0.3 <= 4.1.31 == 5.0.24 == 5.0.12
CVE-2007-1358	Low	May 10, 2007 5/10/07	== 4.0.4 == 4.0.6 == 4.0.3 == 4.0.1 == 4.1.0 == 4.0.2 == 4.0.5 == 4.0.0 <= 4.1.31
CVE-2007-1858	Low	May 10, 2007 5/10/07	== 5.0.19 == 5.5.12 == 5.0.14 == 5.5.14 == 5.5.10 == 5.0.22 == 5.5.4 == 5.5.7 == 5.5.1 == 5.5.11 == 5.5.6 == 5.0.15 == 5.0.30 == 5.5.15 == 5.0.23 == 5.0.2 == 5.5.5 == 5.0.10 == 5.0.21 == 5.0.26 == 5.0.0 == 4.1.31 == 5.5.3 == 5.0.27 == 5.0.16 == 5.5.9 == 5.0.18 == 5.5.2 == 5.0.28 == 5.0.29 == 5.5.0 == 5.5.13 == 4.1.28 == 5.0.13 == 5.5.8 == 5.0.17 == 5.5.16 == 5.5.17 == 5.0.25 == 5.0.1 == 5.0.11 == 5.0.24 == 5.0.12
CVE-2006-7197	High	April 25, 2007 4/25/07	== 5.5.15
CVE-2007-0450	Medium	March 16, 2007 3/16/07	>= 5.0.0 < 5.5.22 >= 6.0.0 < 6.0.10
CVE-2006-3835	Medium	July 25, 2006 7/25/06	== 5.5.12 == 5.5.7 == 5.5.9 == 5.0.28 == 5.5.16
CVE-2005-4703	Medium	December 31, 2005 12/31/05	== 4.0.3
CVE-2005-4836	High	December 31, 2005 12/31/05	== 4.1.35 == 4.1.36 == 4.1.21 == 4.1.24 == 4.1.25 == 4.1.39 == 4.1.27 == 4.1.30 == 4.1.18 == 4.1.40 == 4.1.19 == 4.1.28-alpha == 4.1.31 == 4.1.16 == 4.1.29 == 4.1.22 == 4.1.26 == 4.1.17 == 4.1.33 == 4.1.15 == 4.1.20 == 4.1.23 == 4.1.34 == 4.1.32 == 4.1.37 == 4.1.29-alpha
CVE-2005-4838	Low	December 31, 2005 12/31/05	<= 5.5.6
CVE-2005-3510	Medium	November 6, 2005 11/6/05	== 5.5.10 == 5.5.4 == 5.5.7 == 5.5.1 == 5.5.11 == 5.5.6 == 5.5.5 == 5.5.3 == 5.5.9 == 5.5.2 == 5.5.0 == 5.5.8
CVE-2005-3164	Low	October 6, 2005 10/6/05	>= 4.0.1 <= 4.0.6 >= 4.1.0 <= 4.1.36
CVE-2005-2090	Low	July 5, 2005 7/5/05	== 5.0.19 == 4.1.24
CVE-2005-0808	Medium	May 2, 2005 5/2/05	== 3.1 == 3.2.1 == 3.2.2-beta2 == 3.2.4 == 3.0 == 3.3.1a == 3.1.1 == 3.2.3 == 3.2 == 3.3.1 == 3.3
CVE-2003-0866	Medium	November 17, 2003 11/17/03	== 4.0.4 == 4.0.6 == 4.0.3 == 4.0.1 == 4.0.2 == 4.0.5 == 4.0.0
CVE-2002-1567	Medium	October 6, 2003 10/6/03	== 4.1.0
CVE-2003-0042	Medium	February 7, 2003 2/7/03	== 3.1 == 3.2.1 == 3.2.4 == 3.0 == 3.1.1 == 3.2.3 == 3.2 == 3.3.1 == 3.3
CVE-2003-0043	Medium	February 7, 2003 2/7/03	== 3.1 == 3.2.1 == 3.2.4 == 3.0 == 3.1.1 == 3.2.3 == 3.2 == 3.3.1 == 3.3
CVE-2003-0044	Medium	February 7, 2003 2/7/03	== 3.1 == 3.2.1 == 3.2.4 == 3.0 == 3.3.1a == 3.1.1 == 3.2.3 == 3.2 == 3.3.1 == 3.3
CVE-2003-0045	Medium	February 7, 2003 2/7/03	== 3.1 == 3.2.1 == 3.2.4 == 3.0 == 3.1.1 == 3.2.3 == 3.2 == 3.3.1 == 3.3
CVE-2002-1394	High	January 17, 2003 1/17/03	== 4.0.4 == 4.1.9-beta == 4.0.3 == 4.0.1 == 4.1.3-beta == 4.1.10 == 4.1.0 == 4.0.2 == 4.0.5 == 4.0.0
CVE-2002-1895	Medium	December 31, 2002 12/31/02	== 4.0.4 == 3.3
CVE-2002-2006	Medium	December 31, 2002 12/31/02	== 3.1 == 3.2.1 == 3.2.4 == 3.0 == 4.0.3 == 4.0.1 == 4.1.0 == 3.1.1 == 4.0.2 == 4.0.0 == 3.2.3 == 3.2 == 3.3.1 == 3.3
CVE-2002-2007	Medium	December 31, 2002 12/31/02	== 3.2.4 == 3.2.3
CVE-2002-2008	Medium	December 31, 2002 12/31/02	== 4.0.3
CVE-2002-2009	Medium	December 31, 2002 12/31/02	== 4.0.1
CVE-2002-2272	High	December 31, 2002 12/31/02	== 4.1.2 == 4.0.4 == 4.1.9-beta == 4.0.6 == 4.0.3 == 4.0.1 == 4.1.1 == 4.1.12 == 4.1.3-beta == 4.1.10 == 4.1.0 == 4.0.2 == 4.1.3 == 4.0.5 == 4.0.0
CVE-2002-1148	Medium	October 11, 2002 10/11/02	== 3.1 == 4.0.4 == 3.2.1 == 4.1.9-beta == 3.2.2-beta2 == 3.2.4 == 3.0 == 4.0.3 == 4.0.1 == 4.1.3-beta == 4.1.10 == 4.1.0 == 3.1.1 == 4.0.2 == 4.0.0 == 3.2.3 == 3.2 == 3.3.1 == 3.3
CVE-2002-0935	Medium	October 4, 2002 10/4/02	== 4.0.3
CVE-2002-0936	Medium	October 4, 2002 10/4/02	== 4.0.3
CVE-2002-0493	High	August 12, 2002 8/12/02	<= 3.3.2
CVE-2002-0682	High	July 23, 2002 7/23/02	== 4.0.3
CVE-2000-1210	Medium	March 22, 2002 3/22/02	<= 3.1
CVE-2001-1563	High	December 31, 2001 12/31/01	== 3.2.1
CVE-2001-0829	Medium	December 6, 2001 12/6/01	== 3.2.1
CVE-2001-0917	Medium	November 22, 2001 11/22/01	== 4.0.1
CVE-2001-0590	Medium	August 2, 2001 8/2/01	<= 3.2.2
CVE-2000-0759	Medium	October 20, 2000 10/20/00	== 3.1

Showing vulnerabilities for 2 products matching "tomcat". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.