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,508

Total vulnerabilities in the database

Vulnerabilities for products matching "kerberos_5"

Found 1 matching product.

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

mit / kerberos_5

784 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2012-1015	High	August 6, 2012 8/6/12	== 1.8 == 1.8.1 == 1.8.2 == 1.8.3 == 1.8.4 == 1.8.5 == 1.8.6 == 1.9.4 == 1.10 == 1.10.1 == 1.10.2
CVE-2012-1012	Medium	June 7, 2012 6/7/12	== 1.10 == 1.10.1
CVE-2012-1013	Low	June 7, 2012 6/7/12	== 1.8 == 1.8.1 == 1.8.2 == 1.8.3 == 1.8.4 == 1.8.5 == 1.8.6 == 1.9 == 1.9.1 == 1.9.2 == 1.9.3 == 1.10 == 1.10.1
CVE-2011-4151	High	October 20, 2011 10/20/11	== 1.8 == 1.8.1 == 1.8.2 == 1.8.3 == 1.8.4
CVE-2011-1527	High	October 20, 2011 10/20/11	== 1.9 == 1.9.1
CVE-2011-1528	High	October 20, 2011 10/20/11	== 1.8 == 1.8.1 == 1.8.2 == 1.8.3 == 1.8.4 == 1.9 == 1.9.1
CVE-2011-1529	High	October 20, 2011 10/20/11	== 1.8 == 1.8.1 == 1.8.2 == 1.8.3 == 1.8.4 == 1.9 == 1.9.1
CVE-2011-0285	High	April 15, 2011 4/15/11	== 1.7 == 1.7.1 == 1.8 == 1.8.1 == 1.8.2 == 1.8.3 == 1.9
CVE-2011-0284	High	March 20, 2011 3/20/11	== 1.7 == 1.7.1 == 1.8 == 1.8.1 == 1.8.2 == 1.8.3 == 1.9
CVE-2011-0281	Medium	February 10, 2011 2/10/11	== 1.6 == 1.6.1 == 1.6.2 == 1.7 == 1.7.1 == 1.8 == 1.8.1 == 1.8.2 == 1.8.3 == 1.9
CVE-2011-0282	Medium	February 10, 2011 2/10/11	== 1.6 == 1.6.1 == 1.6.2 == 1.7 == 1.7.1 == 1.8 == 1.8.1 == 1.8.2 == 1.8.3 == 1.9
CVE-2011-0283	Medium	February 10, 2011 2/10/11	== 1.9
CVE-2010-4022	Medium	February 10, 2011 2/10/11	== 1.7 == 1.8 == 1.9
CVE-2010-4020	Low	December 2, 2010 12/2/10	== 1.8 == 1.8.1 == 1.8.2 == 1.8.3
CVE-2010-4021	Low	December 2, 2010 12/2/10	== 1.7
CVE-2010-1323	Low	December 2, 2010 12/2/10	== 1.3-alpha1 == 1.3 == 1.3.1 == 1.3.2 == 1.3.3 == 1.3.4 == 1.3.5 == 1.3.6 == 1.4 == 1.4.1 == 1.4.2 == 1.4.3 == 1.4.4 == 1.5 == 1.5.1 == 1.5.2 == 1.5.3 == 1.6 == 1.6.1 == 1.6.2 == 1.7 == 1.7.1 == 1.8 == 1.8.1 == 1.8.2 == 1.8.3
CVE-2010-1324	Low	December 2, 2010 12/2/10	== 1.7 == 1.7.1 == 1.8 == 1.8.1 == 1.8.2 == 1.8.3
CVE-2010-1322	Medium	October 7, 2010 10/7/10	== 1.8 == 1.8.1 == 1.8.2 == 1.8.3
CVE-2010-1321	Medium	May 19, 2010 5/19/10	>= 1.8 < 1.8.2 <= 1.7.1
CVE-2010-1320	Low	April 22, 2010 4/22/10	== 1.7 == 1.7.1 == 1.8 == 1.8.1
CVE-2010-0629	Medium	April 7, 2010 4/7/10	>= 1.5 <= 1.6.3
CVE-2010-0628	Medium	March 25, 2010 3/25/10	== 1.7 == 1.7.1 == 1.8
CVE-2010-0283	High	February 22, 2010 2/22/10	== 1.7 == 1.7.1
CVE-2009-4212	High	January 13, 2010 1/13/10	== 1.3 == 1.3.1 == 1.3.2 == 1.3.3 == 1.3.4 == 1.3.5 == 1.3.6 == 1.4 == 1.4.1 == 1.4.2 == 1.4.3 == 1.4.4 == 1.5 == 1.5.1 == 1.5.2 == 1.5.3 == 1.6 == 1.6.1 == 1.6.2 == 1.7
CVE-2009-3295	Medium	December 29, 2009 12/29/09	== 1.7
CVE-2009-0844	Medium	April 9, 2009 4/9/09	== 1.5 == 1.5.1 == 1.5.2 == 1.5.3 == 1.6 == 1.6.1 == 1.6.2
CVE-2009-0846	High	April 9, 2009 4/9/09	< 1.6.4
CVE-2009-0845	Medium	March 27, 2009 3/27/09	== 1.5 == 1.5.1 == 1.5.2 == 1.5.3 == 1.6 == 1.6.1 == 1.6.2
CVE-2008-0062	Critical	March 19, 2008 3/19/08	<= 1.6.3
CVE-2008-0063	High	March 19, 2008 3/19/08	<= 1.6.3
CVE-2008-0947	High	March 19, 2008 3/19/08	== 1.6.3 == 1.4 == 1.4.1 == 1.4.2 == 1.4.3 == 1.4.4 == 1.5 == 1.5.1 == 1.5.2 == 1.5.3 == 1.6 == 1.6.1 == 1.6.2
CVE-2008-0948	High	March 19, 2008 3/19/08	== 1.2.2
CVE-2007-5901	Medium	December 6, 2007 12/6/07	<= 1.6.3_kdc
CVE-2007-5971	Medium	December 6, 2007 12/6/07	<= 1.6.3_kdc
CVE-2007-5972	High	December 6, 2007 12/6/07	== 1.5
CVE-2007-4743	High	September 6, 2007 9/6/07	== 1.4 == 1.4.1 == 1.4.2 == 1.4.3 == 1.4.4 == 1.5 == 1.5.1 == 1.5.2 == 1.5.3 == 1.6 == 1.6.1 == 1.6.2
CVE-2007-3999	High	September 5, 2007 9/5/07	== 1.4 == 1.4.1 == 1.4.2 == 1.4.3 == 1.4.4 == 1.5 == 1.5.1 == 1.5.2 == 1.5.3 == 1.6 == 1.6.1 == 1.6.2
CVE-2007-4000	High	September 5, 2007 9/5/07	>= 1.5 <= 1.6.2
CVE-2007-2442	High	June 26, 2007 6/26/07	<= 1.6.1
CVE-2007-2443	High	June 26, 2007 6/26/07	<= 1.6.1
CVE-2007-2798	High	June 26, 2007 6/26/07	<= 1.6.1
CVE-2007-0956	High	April 6, 2007 4/6/07	< 1.6.1
CVE-2007-0957	High	April 6, 2007 4/6/07	< 1.6.1
CVE-2007-1216	High	April 6, 2007 4/6/07	< 1.6.1
CVE-2006-6143	High	December 31, 2006 12/31/06	== 1.4 == 1.4.1 == 1.4.2 == 1.4.3 == 1.4.4 == 1.5 == 1.5.1
CVE-2006-6144	Medium	December 31, 2006 12/31/06	>= 1.5 <= 1.5.1
CVE-2006-3083	High	August 9, 2006 8/9/06	== 1.4 == 1.4.1 == 1.4.2 == 1.4.3 == 1.5
CVE-2006-3084	High	August 9, 2006 8/9/06	== 1.4 == 1.4.1 == 1.4.2 == 1.4.3 == 1.5
CVE-2005-1174	Medium	July 18, 2005 7/18/05	== 1.3 == 1.3.1 == 1.3.2 == 1.3.3 == 1.3.4 == 1.3.5 == 1.3.6 == 1.4 == 1.4.1
CVE-2005-1175	High	July 18, 2005 7/18/05	== 1.3 == 1.3.1 == 1.3.2 == 1.3.3 == 1.3.4 == 1.3.5 == 1.3.6 == 1.4 == 1.4.1

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.