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 "player"

Found 2 matching products. Filters apply to all results.

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

vmware / player

89 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2016-2077	High	May 18, 2016 5/18/16	== 7.0 == 7.1 == 7.1.1 == 7.1.2
CVE-2015-6933	Medium	January 9, 2016 1/9/16	== 7.1 == 7.0 == 7.1.1
CVE-2015-3650	High	July 10, 2015 7/10/15	== 5.0 == 5.0.1 == 5.0.2 == 5.0.3 == 5.0.4 == 6.0 == 6.0.1 == 6.0.2 == 6.0.3 == 6.0.4 == 6.0.5 == 6.0.6 == 7.0 == 7.1
CVE-2015-2341	High	June 13, 2015 6/13/15	== 6.0 == 6.0.4 == 6.0.2 == 6.0.3 == 6.0.5 == 6.0.1
CVE-2015-2340	Medium	June 13, 2015 6/13/15	== 6.0 == 7.1 == 6.0.4 == 7.0 == 6.0.2 == 6.0.3 == 6.0.5 == 6.0.1
CVE-2015-2339	Medium	June 13, 2015 6/13/15	== 6.0 == 7.1 == 6.0.4 == 7.0 == 6.0.2 == 6.0.3 == 6.0.5 == 6.0.1
CVE-2015-2338	Medium	June 13, 2015 6/13/15	== 6.0 == 7.1 == 6.0.4 == 7.0 == 6.0.2 == 6.0.3 == 6.0.5 == 6.0.1
CVE-2015-2336	Medium	June 13, 2015 6/13/15	== 6.0 == 7.1 == 6.0.4 == 7.0 == 6.0.2 == 6.0.3 == 6.0.5 == 6.0.1
CVE-2015-2337	Medium	June 13, 2015 6/13/15	== 6.0 == 7.1 == 6.0.4 == 7.0 == 6.0.2 == 6.0.3 == 6.0.5 == 6.0.1
CVE-2015-1044	Low	January 29, 2015 1/29/15	== 6.0 == 6.0.4 == 6.0.2 == 6.0.3 == 6.0.1
CVE-2015-1043	Low	January 29, 2015 1/29/15	== 6.0 == 6.0.4 == 6.0.2 == 6.0.3 == 6.0.1
CVE-2014-8370	Medium	January 29, 2015 1/29/15	== 6.0 == 6.0.4 == 6.0.2 == 6.0.3 == 6.0.1
CVE-2014-3793	Medium	May 31, 2014 5/31/14	== 6.0 == 6.0.1
CVE-2014-2384	Low	April 15, 2014 4/15/14	== 6.0.1_build_1379776
CVE-2014-1208	Low	January 17, 2014 1/17/14	== 5.0
CVE-2013-3519	High	December 4, 2013 12/4/13	== 5.0.2 == 5.0.1 == 5.0
CVE-2013-5972	High	November 18, 2013 11/18/13	== 5.0.2 == 5.0.1 == 5.0
CVE-2013-1662	Medium	August 24, 2013 8/24/13	== 4.0.3 == 4.0.5 == 4.0.1 == 4.0.2 == 4.0 == 4.0.4 == 4.0.0.18997 == 4.0.6 == 5.0.2 == 5.0.1 == 5.0
CVE-2012-3569	High	November 14, 2012 11/14/12	== 4.0.3 == 4.0.1 == 4.0.2 == 4.0 == 4.0.4 == 4.0.0.18997
CVE-2012-5458	High	November 14, 2012 11/14/12	== 4.0 == 4.0.0.18997 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.4
CVE-2012-5459	High	November 14, 2012 11/14/12	== 4.0 == 4.0.0.18997 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.4
CVE-2012-1666	Medium	September 8, 2012 9/8/12	== 4.0.1 == 4.0.2 == 4.0 == 4.0.0.18997 <= 4.0.3
CVE-2012-3288	High	June 14, 2012 6/14/12	== 3.0 == 3.0.1 == 3.1 == 3.1.1 == 3.1.2 == 3.1.3 == 3.1.4 == 3.1.5 == 4.0 == 4.0.1 == 4.0.2 == 4.0.3
CVE-2012-3289	High	June 14, 2012 6/14/12	== 4.0.3 == 4.0.1 == 4.0.2 == 4.0
CVE-2012-2449	High	May 4, 2012 5/4/12	== 4.0.1 == 4.0.2 == 4.0
CVE-2012-2450	High	May 4, 2012 5/4/12	== 4.0.1 == 4.0.2 == 4.0
CVE-2012-1518	High	April 17, 2012 4/17/12	== 4.0.1 == 4.0.2 == 4.0
CVE-2011-3868	High	October 7, 2011 10/7/11	== 3.0.1 == 3.0 == 3.1.2 == 3.1 == 3.1.3 == 3.1.1 == 3.1.4
CVE-2011-2145	Medium	June 6, 2011 6/6/11	== 3.1 == 3.1.1 == 3.1.2 == 3.1.3
CVE-2011-2146	Low	June 6, 2011 6/6/11	== 3.1.2 == 3.1 == 3.1.3 == 3.1.1
CVE-2011-1787	Medium	June 6, 2011 6/6/11	== 3.1.2 == 3.1 == 3.1.3 == 3.1.1
CVE-2010-4294	High	December 6, 2010 12/6/10	== 2.5 == 2.5.1 == 2.5.2 == 2.5.3 == 2.5.4 == 2.5.5 == 3.0 == 3.0.1 == 3.1 == 3.1.1 == 3.1.2
CVE-2010-4295	Medium	December 6, 2010 12/6/10	== 3.1 == 3.1.1 == 3.1.2
CVE-2010-4296	High	December 6, 2010 12/6/10	== 3.1 == 3.1.1 == 3.1.2
CVE-2010-4297	High	December 6, 2010 12/6/10	== 2.5.4 == 2.5.1 == 2.5.2 == 3.1.2 == 3.1 == 2.5 == 3.1.1 == 2.5.5 == 2.5.3
CVE-2010-3277	Low	September 28, 2010 9/28/10	== 3.0.1 == 3.0 == 3.1 == 3.1.1
CVE-2010-1205	Critical	June 30, 2010 6/30/10	>= 2.5 < 2.5.5 >= 3.1 < 3.1.2
CVE-2010-2249	Medium	June 30, 2010 6/30/10	>= 2.5 < 2.5.5 >= 3.1 < 3.1.2
CVE-2009-4811	Medium	April 27, 2010 4/27/10	== 3.0.1 == 2.5.4 == 2.5.1 == 3.0 == 2.5.2 == 2.5 == 2.5.3
CVE-2009-1564	High	April 12, 2010 4/12/10	== 2.5.1 == 2.5.2 == 2.5 == 2.5.3
CVE-2009-1565	High	April 12, 2010 4/12/10	== 2.5.1 == 2.5.2 == 2.5 == 2.5.3
CVE-2009-3732	High	April 12, 2010 4/12/10	>= 2.5.0 < 2.5.4 == 3.0
CVE-2010-1138	Medium	April 12, 2010 4/12/10	== 3.0 == 2.5 == 2.5.1 == 2.5.2 == 2.5.3
CVE-2010-1139	High	April 12, 2010 4/12/10	== 2.5 == 2.5.1 == 2.5.2 == 2.5.3
CVE-2010-1140	Medium	April 12, 2010 4/12/10	== 3.0
CVE-2010-1141	High	April 12, 2010 4/12/10	== 2.5 == 2.5.1 == 2.5.2 == 2.5.3
CVE-2010-1142	High	April 12, 2010 4/12/10	== 2.5 == 2.5.1 == 2.5.2 == 2.5.3
CVE-2009-2267	Medium	November 2, 2009 11/2/09	== 2.5.1 == 2.5.2 == 2.5
CVE-2009-3707	Medium	October 16, 2009 10/16/09	== 3.0.1 == 2.5.4 == 2.5.1 == 3.0 == 2.5.2 == 2.5 == 2.5.3
CVE-2009-0199	High	September 8, 2009 9/8/09	== 2.5.1 == 2.5.2 == 2.5.2_build_156735 == 2.5

divx / player

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2014-10024	High		January 13, 2015 1/13/15	*

Showing vulnerabilities for 2 products matching "player". 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.