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.

327,921

Total vulnerabilities in the database

Vulnerabilities for products matching "pidgin"

Found 1 matching product.

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

pidgin / pidgin

86 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2011-4603	Medium	December 17, 2011 12/17/11	<= 2.10.0 == 2.5.9 == 2.5.8 == 2.7.9 == 2.7.5 == 2.1.0 == 2.7.4 == 2.6.0 == 2.5.2 == 2.5.1 == 2.6.3 == 2.7.6 == 2.7.11 == 2.5.6 == 2.7.10 == 2.5.7 == 2.0.1 == 2.4.2 == 2.7.3 == 2.5.4 == 2.5.5 == 2.6.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.6.6 == 2.8.0 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.9.0 == 2.2.0 == 2.2.1 == 2.7.8 == 2.7.7 == 2.5.3 == 2.6.1 == 2.6.4 == 2.7.2 == 2.7.1
CVE-2011-4602	Medium	December 17, 2011 12/17/11	<= 2.10.0 == 2.5.9 == 2.5.8 == 2.7.9 == 2.7.5 == 2.1.0 == 2.7.4 == 2.6.0 == 2.5.2 == 2.5.1 == 2.6.3 == 2.7.6 == 2.7.11 == 2.5.6 == 2.7.10 == 2.5.7 == 2.0.1 == 2.4.2 == 2.7.3 == 2.5.4 == 2.5.5 == 2.6.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.6.6 == 2.8.0 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.9.0 == 2.2.0 == 2.2.1 == 2.7.8 == 2.7.7 == 2.5.3 == 2.6.1 == 2.6.4 == 2.7.2 == 2.7.1
CVE-2011-3594	Low	November 4, 2011 11/4/11	*
CVE-2011-3184	Low	August 29, 2011 8/29/11	== 2.5.9 == 2.5.8 == 2.7.9 == 2.7.5 == 2.7.0 == 2.1.0 == 2.7.4 == 2.6.0 == 2.5.2 == 2.5.1 == 2.7.6 == 2.7.11 == 2.5.6 == 2.7.10 == 2.5.7 == 2.0.1 == 2.4.2 == 2.7.3 == 2.5.4 == 2.5.5 == 2.6.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.6.6 == 2.8.0 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.2.0 == 2.2.1 == 2.7.8 <= 2.9.0 == 2.7.7 == 2.5.3 == 2.6.1 == 2.6.4 == 2.7.2 == 2.7.1
CVE-2011-3185	High	August 29, 2011 8/29/11	<= 2.9.0 == 2.0.0 == 2.0.1 == 2.0.2 == 2.1.0 == 2.1.1 == 2.2.0 == 2.2.1 == 2.2.2 == 2.3.0 == 2.3.1 == 2.4.0 == 2.4.1 == 2.4.2 == 2.4.3 == 2.5.0 == 2.5.1 == 2.5.2 == 2.5.3 == 2.5.4 == 2.5.5 == 2.5.6 == 2.5.7 == 2.5.8 == 2.5.9 == 2.6.0 == 2.6.1 == 2.6.2 == 2.6.4 == 2.6.5 == 2.6.6 == 2.7.0 == 2.7.1 == 2.7.2 == 2.7.3 == 2.7.4 == 2.7.5 == 2.7.6 == 2.7.7 == 2.7.8 == 2.7.9 == 2.7.10 == 2.7.11 == 2.8.0
CVE-2011-2943	Low	August 29, 2011 8/29/11	== 2.5.9 == 2.5.8 == 2.7.9 == 2.7.5 == 2.7.0 == 2.1.0 == 2.7.4 == 2.6.0 == 2.5.2 == 2.5.1 == 2.7.6 == 2.7.11 == 2.5.6 == 2.7.10 == 2.5.7 == 2.0.1 == 2.4.2 == 2.7.3 == 2.5.4 == 2.5.5 == 2.6.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.6.6 == 2.8.0 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.2.0 == 2.2.1 == 2.7.8 <= 2.9.0 == 2.7.7 == 2.5.3 == 2.6.1 == 2.6.4 == 2.7.2 == 2.7.1
CVE-2011-1091	Low	March 14, 2011 3/14/11	== 2.7.9 == 2.7.5 == 2.7.0 == 2.7.4 == 2.6.0 == 2.7.6 == 2.7.10 == 2.7.3 == 2.6.5 == 2.6.6 == 2.6.2 == 2.7.8 == 2.7.7 == 2.6.1 == 2.6.4 == 2.7.2 == 2.7.1
CVE-2010-4528	Low	January 7, 2011 1/7/11	== 2.5.9 == 2.5.8 == 2.7.5 == 2.7.0 == 2.1.0 <= 2.7.8 == 2.7.4 == 2.6.0 == 2.5.2 == 2.5.1 == 2.7.6 == 2.5.6 == 2.5.7 == 2.0.1 == 2.4.2 == 2.7.3 == 2.5.4 == 2.5.5 == 2.6.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.6.6 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.2.0 == 2.2.1 == 2.7.7 == 2.5.3 == 2.6.1 == 2.6.4 == 2.7.2 == 2.7.1
CVE-2010-3711	Low	October 28, 2010 10/28/10	== 2.5.9 == 2.5.8 <= 2.7.3 == 2.7.0 == 2.1.0 == 2.6.0 == 2.5.2 == 2.5.1 == 2.5.6 == 2.5.7 == 2.0.1 == 2.4.2 == 2.5.4 == 2.5.5 == 2.6.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.6.6 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.2.0 == 2.2.1 == 2.5.3 == 2.6.1 == 2.6.4 == 2.7.2 == 2.7.1
CVE-2010-2528	Low	July 30, 2010 7/30/10	== 2.5.9 == 2.5.8 == 2.7.0 == 2.1.0 == 2.6.0 == 2.5.2 == 2.5.1 <= 2.7.1 == 2.5.6 == 2.5.7 == 2.0.1 == 2.4.2 == 2.5.4 == 2.5.5 == 2.6.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.6.6 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.2.0 == 2.2.1 == 2.5.3 == 2.6.1 == 2.6.4
CVE-2010-1624	Medium	May 14, 2010 5/14/10	< 2.7.0
CVE-2010-0420	Low	February 24, 2010 2/24/10	== 2.5.9 == 2.5.8 == 2.1.0 == 2.6.0 == 2.5.2 == 2.5.1 == 2.5.6 == 2.5.7 == 2.0.1 == 2.4.2 == 2.5.4 == 2.5.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.2.0 == 2.2.1 <= 2.6.5 == 2.5.3 == 2.6.1 == 2.6.4
CVE-2010-0423	Medium	February 24, 2010 2/24/10	== 2.5.9 == 2.5.8 == 2.1.0 == 2.6.0 == 2.5.2 == 2.5.1 == 2.5.6 == 2.5.7 == 2.0.1 == 2.4.2 == 2.5.4 == 2.5.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.2.0 == 2.2.1 <= 2.6.5 == 2.5.3 == 2.6.1 == 2.6.4
CVE-2010-0013	High	January 9, 2010 1/9/10	== 2.6.4
CVE-2010-0277	Medium	January 9, 2010 1/9/10	== 2.5.9 == 2.5.8 == 2.1.0 == 2.6.0 == 2.5.2 == 2.5.1 == 2.5.6 == 2.5.7 == 2.0.1 == 2.4.2 == 2.5.4 == 2.5.5 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.6.2 == 2.5.0 == 2.2.0 == 2.2.1 <= 2.6.5 == 2.5.3 == 2.6.1 == 2.6.4
CVE-2009-3615	Medium	October 20, 2009 10/20/09	<= 2.6.2 == 2.0.0 == 2.0.1 == 2.0.2 == 2.1.0 == 2.1.1 == 2.2.0 == 2.2.1 == 2.2.2 == 2.3.0 == 2.3.1 == 2.4.0 == 2.4.1 == 2.4.2 == 2.4.3 == 2.5.0 == 2.5.1 == 2.5.2 == 2.5.3 == 2.5.4 == 2.5.5 == 2.5.6 == 2.5.7 == 2.5.8 == 2.5.9 == 2.6.0 == 2.6.1
CVE-2009-2703	Medium	September 8, 2009 9/8/09	<= 2.6.1 == 2.0.0 == 2.0.1 == 2.0.2 == 2.1.0 == 2.1.1 == 2.2.0 == 2.2.1 == 2.2.2 == 2.3.0 == 2.3.1 == 2.4.0 == 2.4.0-32_bit == 2.4.1-32_bit == 2.4.1 == 2.4.2-32_bit == 2.4.2 == 2.4.3 == 2.4.3-32_bit == 2.5.0 == 2.5.0-32_bit == 2.5.1 == 2.5.2 == 2.5.2-32_bit == 2.5.3-32_bit == 2.5.3 == 2.5.4-32_bit == 2.5.4 == 2.5.5 == 2.5.5-32_bit == 2.5.6 == 2.5.7 == 2.5.8 == 2.5.9 == 2.6.0
CVE-2009-3083	Medium	September 8, 2009 9/8/09	<= 2.6.1 == 2.0.0 == 2.0.1 == 2.0.2 == 2.1.0 == 2.1.1 == 2.2.0 == 2.2.1 == 2.2.2 == 2.3.0 == 2.3.1 == 2.4.0 == 2.4.0-32_bit == 2.4.1-32_bit == 2.4.1 == 2.4.2-32_bit == 2.4.2 == 2.4.3 == 2.4.3-32_bit == 2.5.0 == 2.5.0-32_bit == 2.5.1 == 2.5.2 == 2.5.2-32_bit == 2.5.3-32_bit == 2.5.3 == 2.5.4-32_bit == 2.5.4 == 2.5.5 == 2.5.5-32_bit == 2.5.6 == 2.5.7 == 2.5.8 == 2.5.9 == 2.6.0
CVE-2009-3084	Medium	September 8, 2009 9/8/09	<= 2.6.1 == 2.0.0 == 2.0.1 == 2.0.2 == 2.1.0 == 2.1.1 == 2.2.0 == 2.2.1 == 2.2.2 == 2.3.0 == 2.3.1 == 2.4.0 == 2.4.0-32_bit == 2.4.1-32_bit == 2.4.1 == 2.4.2-32_bit == 2.4.2 == 2.4.3 == 2.4.3-32_bit == 2.5.0 == 2.5.0-32_bit == 2.5.1 == 2.5.2 == 2.5.2-32_bit == 2.5.3-32_bit == 2.5.3 == 2.5.4-32_bit == 2.5.4 == 2.5.5 == 2.5.5-32_bit == 2.5.6 == 2.5.7 == 2.5.8 == 2.5.9 == 2.6.0
CVE-2009-3085	Medium	September 8, 2009 9/8/09	<= 2.6.1 == 2.0.0 == 2.0.1 == 2.0.2 == 2.1.0 == 2.1.1 == 2.2.0 == 2.2.1 == 2.2.2 == 2.3.0 == 2.3.1 == 2.4.0 == 2.4.0-32_bit == 2.4.1-32_bit == 2.4.1 == 2.4.2-32_bit == 2.4.2 == 2.4.3 == 2.4.3-32_bit == 2.5.0 == 2.5.0-32_bit == 2.5.1 == 2.5.2 == 2.5.2-32_bit == 2.5.3-32_bit == 2.5.3 == 2.5.4-32_bit == 2.5.4 == 2.5.5 == 2.5.5-32_bit == 2.5.6 == 2.5.7 == 2.5.8 == 2.5.9 == 2.6.0
CVE-2009-3025	Low	August 31, 2009 8/31/09	== 2.6.0
CVE-2009-3026	Medium	August 31, 2009 8/31/09	== 2.6.0
CVE-2009-2694	High	August 21, 2009 8/21/09	== 2.1.0 == 2.5.2 == 2.5.1 == 2.5.6 == 2.5.7 == 2.0.1 == 2.4.2 == 2.5.4 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 <= 2.5.8 == 2.5.0 == 2.2.0 == 2.2.1 == 2.5.3
CVE-2009-1889	Medium	July 1, 2009 7/1/09	== 2.1.0 == 2.5.3-32_bit == 2.5.2 == 2.5.1 == 2.5.6 == 2.0.1 == 2.4.2 == 2.5.4 == 2.5.5 == 2.2.2 == 2.1.1 <= 2.5.7 == 2.3.1 == 2.4.3 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.5.0 == 2.5.5-32_bit == 2.2.0 == 2.2.1 == 2.5.4-32_bit == 2.5.3
CVE-2009-1373	High	May 26, 2009 5/26/09	== 2.1.0 == 2.5.2 == 2.5.1 == 2.0.1 == 2.4.2 == 2.5.4 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 <= 2.5.5 == 2.5.0 == 2.2.0 == 2.2.1 == 2.5.3
CVE-2009-1374	Medium	May 26, 2009 5/26/09	== 2.1.0 == 2.5.2 == 2.5.1 == 2.0.1 == 2.4.2 == 2.5.4 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 <= 2.5.5 == 2.5.0 == 2.2.0 == 2.2.1 == 2.5.3
CVE-2009-1375	Medium	May 26, 2009 5/26/09	== 2.1.0 == 2.5.2 == 2.5.1 == 2.0.1 == 2.4.2 == 2.5.4 == 2.2.2 == 2.1.1 == 2.3.1 == 2.4.3 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 <= 2.5.5 == 2.5.0 == 2.2.0 == 2.2.1 == 2.5.3
CVE-2009-1376	High	May 26, 2009 5/26/09	== 2.5.2-32_bit == 2.5.3-32_bit == 2.5.0-32_bit == 2.4.2-32_bit <= 2.5.5 == 2.4.0-32_bit == 2.4.3-32_bit == 2.5.4-32_bit == 2.4.1-32_bit
CVE-2008-3532	Medium	August 8, 2008 8/8/08	== 2.4.3
CVE-2008-2927	Medium	July 7, 2008 7/7/08	== 2.1.0 == 2.0.1 == 2.2.2 == 2.1.1 == 2.3.1 == 2.0.0 == 2.0.2 == 2.3.0 == 2.4.1 == 2.4.0 == 2.2.0 <= 2.4.2 == 2.2.1
CVE-2008-2955	Low	July 1, 2008 7/1/08	== 2.4.1
CVE-2008-2956	Medium	July 1, 2008 7/1/08	== 2.0.0
CVE-2008-2957	Medium	July 1, 2008 7/1/08	== 2.0.0
CVE-2007-4999	Low	October 29, 2007 10/29/07	== 2.1.0 == 2.2.0 == 2.2.1
CVE-2007-4996	Low	October 1, 2007 10/1/07	== 2.2.0
CVE-2007-3841	High	July 17, 2007 7/17/07	== 2.0.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.