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.

325,981

Total vulnerabilities in the database

Vulnerabilities for products matching "kde"

Found 1 matching product.

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

kde / kde

66 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2012-4512	High	February 8, 2020 2/8/20	== 4.7.3
CVE-2012-4513	Medium	November 11, 2012 11/11/12	== 4.7.3
CVE-2012-4514	Medium	November 11, 2012 11/11/12	== 3.3.2 == 2.2.1 == 3.0_beta_1 == 2.1.2 == 2.0 == 4.0.3 == 4.0.2 == 3.0.2 == 3.0.5 == 2.0_beta == 2.2 == 3.2.0_beta1 == 3.3.1 == 3.1.1a == 3.5.5 == 2.0.1 == 2.2_beta1 == 3.2.2 == 3.2.1 <= 4.9.2 == 3.1.5 == 3.4.3 == 1.x == 3.5.2 == 3.0.5b == 4.7.3 == 4.0.0 == 3.1.0 == 3.4.0 == 3.1.2 == 2.1 == 3.0.1 == 3.0.5a == 2.1_beta2 == 3.0_beta_2 == 3.0.4 == 3.0 == 3.4 == 3.1_beta2 == 3.5.0 == 2.1.1 == 3.5.4 == 1.1.2 == 3.3.x == 1.1.1 == 3.5.7 == 3.5 == 3.5.8 == 3.5.9 == 3.1.3 == 3.5.3 == 3.2.0 == 2.2.2 == 3.1 == 3.1_alpha1 == 3.1.4 == 1.1 == 4.9.0 == 1.2 == 1.0 == 3.3 == 3.5.1 == 3.5.10 == 3.0.3 == 2.1_beta1 == 3.2 == 3.1.1 == 3.0.3a == 3.2.3 == 4.9.1 == 3.4.2 == 4.0.1 == 3.5.6 == 3.1_beta1 == 3.4.1 == 3.3.0 == 3.2.x
CVE-2012-4515	Medium	November 11, 2012 11/11/12	== 4.7.3
CVE-2008-1670	High	April 28, 2008 4/28/08	== 4.0.3 == 4.0.2 == 4.0.0 == 4.0.1
CVE-2008-1671	Low	April 28, 2008 4/28/08	== 3.5.5 == 3.5.7 == 3.5.8 == 3.5.9 == 3.5.6
CVE-2007-5963	Low	December 19, 2007 12/19/07	*
CVE-2007-4569	Medium	September 21, 2007 9/21/07	== 3.3.2 == 3.3.1 == 3.5.5 == 3.4.3 == 3.5.2 == 3.4.0 == 3.4 == 3.5.0 == 3.5.4 == 3.5.7 == 3.5 == 3.5.3 == 3.3 == 3.5.1 == 3.4.2 == 3.5.6 == 3.4.1 == 3.3.0
CVE-2007-0104	Medium	January 9, 2007 1/9/07	== 3.2 == 3.2.1 == 3.2.2 == 3.2.3 == 3.3 == 3.3.1 == 3.3.2 == 3.4 == 3.4.1 == 3.4.2 == 3.4.3 == 3.5
CVE-2006-2933	Low	July 27, 2006 7/27/06	== 3.1.2 == 3.1.3
CVE-2006-2449	Low	June 15, 2006 6/15/06	== 3.3.2 == 3.3.1 == 3.2.2 == 3.2.1 == 3.4.3 == 3.5.2 == 3.4 == 3.5 == 3.5.3 == 3.3 == 3.2 == 3.2.3 == 3.4.2 == 3.4.1
CVE-2006-0019	High	January 20, 2006 1/20/06	== 3.3.2 == 3.2.0_beta1 == 3.3.1 == 3.2.2 == 3.2.1 == 3.4.0 == 3.4 == 3.5.0 == 3.3.x == 3.2.0 == 3.3 == 3.2 == 3.2.3 == 3.4.2 == 3.4.1 == 3.3.0 == 3.2.x
CVE-2005-2494	High	September 6, 2005 9/6/05	== 3.3.2 == 3.3.1 == 3.2.2 == 3.2.1 == 3.4.0 == 3.2.0 == 3.2.3 == 3.4.2 == 3.4.1 == 3.3.0
CVE-2005-2101	Medium	August 17, 2005 8/17/05	== 3.3.2 == 3.0.2 == 3.0.5 == 3.2.0_beta1 == 3.3.1 == 3.2.2 == 3.2.1 == 3.1.5 == 3.1.2 == 3.0.1 == 3.0.5a == 3.0.4 == 3.0 == 3.4 == 3.1_beta2 == 3.1.3 == 3.1 == 3.1_alpha1 == 3.1.4 == 3.3 == 3.0.3 == 3.2 == 3.1.1 == 3.2.3 == 3.4.2 == 3.1_beta1 == 3.4.1
CVE-2005-1852	High	July 26, 2005 7/26/05	== 3.3.2 == 3.3.1 == 3.4.0 == 3.4 == 3.3 == 3.2.3 == 3.4.1
CVE-2005-1920	High	July 26, 2005 7/26/05	>= 3.2 <= 3.4.0
CVE-2005-0011	High	May 2, 2005 5/2/05	== 3.3.2 == 3.3.1 == 3.3
CVE-2005-0078	Low	May 2, 2005 5/2/05	== 1.0 == 1.1 == 1.1.1 == 1.1.2 == 2.0 == 2.0.1 == 2.1 == 2.1_beta1 == 2.1_beta2 == 2.2 == 2.2_beta1 == 2.2.1 == 3.0 == 3.0_beta_1 == 3.0_beta_2 == 3.0.1 == 3.0.2 == 3.0.3 == 3.0.4
CVE-2005-0205	Low	May 2, 2005 5/2/05	== 3.1.5 == 3.1.2 == 3.1.3 == 3.1 == 3.1.4 == 3.1.1
CVE-2005-0237	Medium	May 2, 2005 5/2/05	== 3.2.1
CVE-2005-0365	Low	May 2, 2005 5/2/05	== 3.3.x == 3.2.x
CVE-2005-0404	Medium	May 2, 2005 5/2/05	== 3.3.2
CVE-2005-1046	High	May 2, 2005 5/2/05	== 3.4.0
CVE-2005-0206	High	April 27, 2005 4/27/05	== 3.3.1 == 3.2.2 == 3.2.1 == 3.3 == 3.2 == 3.2.3
CVE-2005-0754	High	April 22, 2005 4/22/05	== 3.3.2 == 3.3.1 == 3.2.2 == 3.2.1 == 3.4 == 3.3 == 3.2 == 3.2.3
CVE-2004-0886	Medium	January 27, 2005 1/27/05	== 3.3.1 == 3.2.2 == 3.2.1 == 3.3 == 3.2 == 3.2.3
CVE-2004-0888	High	January 27, 2005 1/27/05	== 3.3.1 == 3.2.2 == 3.2.1 == 3.3 == 3.2 == 3.2.3
CVE-2004-0889	High	January 27, 2005 1/27/05	== 3.3.1 == 3.2.2 == 3.2.1 == 3.3 == 3.2 == 3.2.3
CVE-2004-1125	High	January 10, 2005 1/10/05	== 3.3.2 == 3.2.3
CVE-2004-1171	Low	January 10, 2005 1/10/05	== 3.3.2 == 3.3.1 == 3.2.2 == 3.2.1 == 3.3 == 3.2 == 3.2.3
CVE-2004-1491	Medium	December 31, 2004 12/31/04	== 3.2.3
CVE-2004-0803	High	December 23, 2004 12/23/04	== 3.3.1 == 3.2.2 == 3.2.1 == 3.3 == 3.2 == 3.2.3
CVE-2004-0746	High	October 20, 2004 10/20/04	== 3.1.3 == 3.2
CVE-2004-0690	Low	September 28, 2004 9/28/04	== 3.2.1
CVE-2004-0689	High	September 28, 2004 9/28/04	< 3.3
CVE-2003-0988	High	February 17, 2004 2/17/04	== 3.1.0 == 3.1.2 == 3.1.3 == 3.1.1
CVE-2003-0690	High	October 6, 2003 10/6/03	== 2.2.1 == 2.1.2 == 2.0 == 3.0.2 == 3.0.5 == 2.0_beta == 2.2 == 3.1.1a == 2.0.1 == 1.1 == 1.1.1 == 2.1.1 == 3.0.3a == 3.0.4 == 3.1.2 == 3.1.3 == 3.0 == 3.0.1 == 3.0.5b == 3.1 == 2.1 == 3.0.3 == 3.1.1 == 1.1.2 == 1.2 == 2.2.2 == 3.0.5a
CVE-2003-0692	High	October 6, 2003 10/6/03	== 2.2.1 == 2.1.2 == 2.0 == 3.0.2 == 3.0.5 == 2.0_beta == 2.2 == 3.1.1a == 2.0.1 == 2.1 == 3.0.1 == 3.1 == 3.1.1 == 1.1.1 == 1.1.2 == 3.0.4 == 3.1.3 == 1.2 == 2.2.2 == 3.0 == 3.0.5a == 3.0.5b == 1.1 == 2.1.1 == 3.0.3 == 3.0.3a == 3.1.2
CVE-2003-0370	High	June 16, 2003 6/16/03	<= 2.2.2
CVE-2003-0204	High	May 5, 2003 5/5/03	== 2.2.1 == 2.1.2 == 2.0 == 3.0.2 == 3.0.5 == 2.2 == 2.0.1 == 2.1 == 3.0.1 == 2.2.2 == 3.0 == 3.1 == 3.1.1 == 2.1.1 == 3.0.3 == 3.0.3a == 3.0.4 == 3.0.5a
CVE-2002-1393	High	January 17, 2003 1/17/03	== 2.2.1 == 2.1.2 == 2.0 == 3.0.2 == 3.0.5 == 2.2 == 2.0.1 == 2.1 == 3.0.1 == 3.0.4 == 3.0 == 2.1.1 == 2.2.2 == 3.0.3 == 3.0.3a
CVE-2002-2333	Medium	December 31, 2002 12/31/02	== 2.2.1 == 2.1.2 == 3.0.2 == 2.2 == 2.1 == 3.0 == 2.1.1 == 2.2.2
CVE-2002-1247	High	November 29, 2002 11/29/02	== 2.0 == 3.0.2 == 2.2 == 2.1 == 3.0.1 == 3.0.4 == 3.0 == 3.0.3 == 3.0.3a
CVE-2002-1281	High	November 29, 2002 11/29/02	== 2.2.1 == 2.1.2 == 3.0.2 == 2.2 == 2.1 == 3.0.1 == 3.0.4 == 3.0 == 2.1.1 == 2.2.2 == 3.0.3
CVE-2002-1282	High	November 29, 2002 11/29/02	== 2.2.1 == 2.1.2 == 3.0.2 == 2.2 == 2.1 == 3.0.1 == 3.0.4 == 3.0 == 2.1.1 == 2.2.2 == 3.0.3
CVE-2002-1306	High	November 29, 2002 11/29/02	== 2.2.1 == 2.1.2 == 3.0.2 == 2.2 == 2.1 == 3.0.1 == 3.0 == 2.1.1 == 2.2.2 == 3.0.3
CVE-2002-1223	High	October 28, 2002 10/28/02	== 1.1 == 3.0.3a
CVE-2002-1224	Medium	October 28, 2002 10/28/02	== 3.0.2 == 3.0.1 == 3.0.3 == 3.0.3a
CVE-2002-1151	High	October 11, 2002 10/11/02	== 3.0.2 == 3.0.1 == 3.0 == 2.2.2 == 3.0.3
CVE-2002-1152	High	October 11, 2002 10/11/02	== 3.0.2 == 3.0.1 == 3.0

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.