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.

328,409

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

132 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-37371	Critical	June 28, 2024 6/28/24	< 1.21.3
CVE-2024-37370	High	June 28, 2024 6/28/24	< 1.21.3
CVE-2024-26462	Medium	February 29, 2024 2/29/24	== 1.21.2
CVE-2024-26461	High	February 29, 2024 2/29/24	== 1.21.2
CVE-2024-26458	Medium	February 29, 2024 2/29/24	== 1.21.2
CVE-2023-39975	High	August 16, 2023 8/16/23	>= 1.21 < 1.21.2
CVE-2023-36054	Medium	August 7, 2023 8/7/23	== 1.21-beta1 == 1.21 < 1.20.2
CVE-2022-42898	High	December 25, 2022 12/25/22	>= 1.8 < 1.19.4 == 1.20-beta1 == 1.20
CVE-2022-39028	High	August 30, 2022 8/30/22	<= 1.0.3
CVE-2021-37750	Medium	August 23, 2021 8/23/21	< 1.18.5 >= 1.19.0 < 1.19.3
CVE-2021-36222	High	July 22, 2021 7/22/21	< 1.18.4 >= 1.19.0 < 1.19.2
CVE-2020-28196	High	November 6, 2020 11/6/20	< 1.17.2 >= 1.18.0 < 1.18.3
CVE-2019-14844	High	September 26, 2019 9/26/19	>= 1.16.1 <= 1.17.1
CVE-2017-7562	Medium	July 26, 2018 7/26/18	>= 1.0 < 1.16.1
CVE-2018-5730	Low	March 6, 2018 3/6/18	>= 5-1.6 < 5-1.21.2
CVE-2018-5729	Low	March 6, 2018 3/6/18	>= 5-1.6 < 5-1.21.2
CVE-2017-15088	Critical	November 23, 2017 11/23/17	<= 1.15.2
CVE-2017-11462	High	September 13, 2017 9/13/17	== 1.14-alpha1 == 1.14-beta1 == 1.14-beta2 == 1.14 == 1.14.1 == 1.14.2 == 1.14.3 == 1.14.4 == 1.14.5 == 1.15 == 1.15.1-beta1 == 1.15.1 == 1.15.1-beta2
CVE-2017-11368	Low	August 9, 2017 8/9/17	== 1.10 == 1.10.1 == 1.10.2 == 1.10.3 == 1.10.4 == 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1 == 1.12.2 == 1.12.3 == 1.13 == 1.13.1 == 1.13.2 == 1.13.3 == 1.13.5 == 1.13.6 == 1.14 == 1.14-alpha1 == 1.14-beta1 == 1.14-beta2 == 1.14.1 == 1.14.2 == 1.14.3 == 1.14.4 == 1.14.5 == 1.15 == 1.15.1 == 1.15.1-beta1 == 1.15.1-beta2 == 1.7 == 1.7.1 == 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.9.4
CVE-2016-3120	Low	August 1, 2016 8/1/16	== 1.13 == 1.13.1 == 1.13.2 == 1.13.3 == 1.13.4 == 1.13.5 == 1.13.6 == 1.14 == 1.14.1 == 1.14.2
CVE-2016-3119	Low	March 26, 2016 3/26/16	== 1.1 == 1.2 == 1.2.1 == 1.2.2 == 1.2.3 == 1.2.4 == 1.2.5 == 1.2.6 == 1.2.7 == 1.2.8 == 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 == 1.8.4 == 1.8.5 == 1.8.6 == 1.9 == 1.9.1 == 1.9.2 == 1.9.3 == 1.9.4 == 1.10 == 1.10.1 == 1.10.2 == 1.10.3 == 1.10.4 == 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1 == 1.12.2 == 1.12.3 == 1.13 == 1.13.1 == 1.13.2 == 1.13.3 == 1.13.4 == 1.14-alpha1 == 1.14-beta1 == 1.14-beta2 == 1.14.0 == 1.14.1 == 1.0 == 1.0.6 == 1.1.1 == 1.2-beta1 == 1.2-beta2
CVE-2015-8631	Medium	February 13, 2016 2/13/16	< 1.13.4 >= 1.14 < 1.14.1
CVE-2015-8630	Medium	February 13, 2016 2/13/16	== 1.12 == 1.12.1 == 1.12.2 == 1.12.3 == 1.12.4 == 1.12.5 == 1.13 == 1.13.1 == 1.13.2 == 1.13.3 == 1.14-alpha1 == 1.14-beta1 == 1.14-beta2 == 1.14
CVE-2015-8629	Medium	February 13, 2016 2/13/16	< 1.13.4 >= 1.14 < 1.14.1
CVE-2015-2698	High	November 13, 2015 11/13/15	== 1.14-beta2
CVE-2015-2697	Low	November 9, 2015 11/9/15	< 1.14
CVE-2015-2696	High	November 9, 2015 11/9/15	< 1.14
CVE-2015-2695	Medium	November 9, 2015 11/9/15	< 1.14
CVE-2015-2694	Medium	May 25, 2015 5/25/15	== 1.12 == 1.12.1 == 1.12.2 == 1.12.3 == 1.13 == 1.13.1
CVE-2014-5355	Medium	February 20, 2015 2/20/15	== 1.1 == 1.2 == 1.2.1 == 1.2.2 == 1.2.3 == 1.2.4 == 1.2.5 == 1.2.6 == 1.2.7 == 1.2.8 == 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 == 1.8.4 == 1.8.5 == 1.8.6 == 1.9 == 1.9.1 == 1.9.2 == 1.9.3 == 1.9.4 == 1.10 == 1.10.1 == 1.10.2 == 1.10.3 == 1.10.4 == 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1 == 1.12.2 == 1.13 == 1.13.1
CVE-2014-9423	Medium	February 19, 2015 2/19/15	== 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1 == 1.12.2 == 1.13
CVE-2014-9422	Medium	February 19, 2015 2/19/15	== 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1 == 1.12.2 == 1.13
CVE-2014-9421	High	February 19, 2015 2/19/15	== 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1 == 1.12.2 == 1.13
CVE-2014-5352	High	February 19, 2015 2/19/15	== 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1 == 1.12.2 == 1.13
CVE-2014-5354	Low	December 16, 2014 12/16/14	== 1.12 == 1.12.1 == 1.12.2
CVE-2014-5353	Low	December 16, 2014 12/16/14	< 1.13.1
CVE-2014-5351	Low	October 10, 2014 10/10/14	== 1.12.2
CVE-2014-4345	High	August 14, 2014 8/14/14	== 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.8.4 == 1.8.5 == 1.8.6 == 1.9 == 1.9.1 == 1.9.2 == 1.9.3 == 1.9.4 == 1.10 == 1.10.1 == 1.10.2 == 1.10.3 == 1.10.4 == 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1
CVE-2014-4343	High	August 14, 2014 8/14/14	== 1.10 == 1.10.1 == 1.10.2 == 1.10.3 == 1.10.4 == 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1
CVE-2014-4344	High	August 14, 2014 8/14/14	== 1.10 == 1.10.1 == 1.10.2 == 1.10.3 == 1.10.4 == 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.11.5 == 1.12 == 1.12.1
CVE-2014-4341	Medium	July 20, 2014 7/20/14	< 1.12.2
CVE-2014-4342	Medium	July 20, 2014 7/20/14	== 1.10 == 1.10.1 == 1.10.2 == 1.10.3 == 1.10.4 == 1.11 == 1.11.1 == 1.11.2 == 1.11.3 == 1.11.4 == 1.12 == 1.12.1 == 1.7 == 1.7.1 == 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.9.4
CVE-2013-1417	Low	November 20, 2013 11/20/13	== 1.11 == 1.11.1 == 1.11.2 == 1.11.3
CVE-2013-1418	Low	November 18, 2013 11/18/13	< 1.10.7
CVE-2013-6800	Low	November 18, 2013 11/18/13	== 1.10 == 1.10.1 == 1.10.2 == 1.10.3 == 1.10.4
CVE-2002-2443	Medium	May 29, 2013 5/29/13	< 1.11.3
CVE-2013-1416	Low	April 19, 2013 4/19/13	< 1.10.5
CVE-2013-1415	Medium	March 5, 2013 3/5/13	< 1.10.4 == 1.11
CVE-2012-1016	Medium	March 5, 2013 3/5/13	< 1.10.4
CVE-2012-1014	High	August 6, 2012 8/6/12	== 1.10 == 1.10.1 == 1.10.2

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.