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

Found 2 matching products. Filters apply to all results.

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

mplayer / mplayer

28 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2011-0723	Medium	May 20, 2011 5/20/11	*
CVE-2008-5616	High	December 17, 2008 12/17/08	== 0.92 <= 1.0_rc1 == 1.0_pre2 == 0.90 == 1.0_pre1 == 0.90_rc == 1.0_pre5try2 == 0.92.1 == 1.0_pre3 == 1.0_pre7try2 == 0.92_cvs == 1.0_pre5 == 0.91 == 1.0_pre5try1 == 1.0_pre3try2 == 1.0_pre7 == 1.0_pre6 == 0.90_pre == 0.90_rc4 == 1.0_pre4
CVE-2008-4610	Medium	October 20, 2008 10/20/08	== 0.92 <= 1.0_rc1 == 1.0_pre2 == 0.90 == 1.0_pre1 == 0.90_rc == 1.0_pre5try2 == 0.92.1 == 1.0_pre3 == 1.0_pre7try2 == 0.92_cvs == 1.0_pre5 == 0.91 == 1.0_pre5try1 == 1.0_pre3try2 == 1.0_pre7 == 1.0_pre6 == 0.90_pre == 0.90_rc4 == 1.0_pre4
CVE-2007-6718	Low	October 20, 2008 10/20/08	== 0.92 <= 1.0_rc1 == 1.0_pre2 == 0.90 == 1.0_pre1 == 0.90_rc == 1.0_pre5try2 == 0.92.1 == 1.0_pre3 == 1.0_pre7try2 == 0.92_cvs == 1.0_pre5 == 0.91 == 1.0_pre5try1 == 1.0_pre3try2 == 1.0_pre7 == 1.0_pre6 == 0.90_pre == 0.90_rc4 == 1.0_pre4
CVE-2008-3827	High	September 29, 2008 9/29/08	== 0.92 == 1.0_pre2 == 0.90 == 1.0_pre1 == 0.90_rc == 1.0_pre5try2 == 1.0_rc1 == 0.92.1 == 1.0_pre3 == 1.0_pre7try2 == 0.92_cvs == 1.0_pre5 == 0.91 == 1.0_pre5try1 == 1.0_pre3try2 == 1.0_pre7 == 1.0_pre6 <= 1.0_rc2 == 0.90_pre == 0.90_rc4 == 1.0_pre4
CVE-2008-1558	High	March 31, 2008 3/31/08	== 1.0_rc2
CVE-2008-0629	Low	February 6, 2008 2/6/08	== 1.02rc2
CVE-2008-0630	Medium	February 6, 2008 2/6/08	== 1.02rc2
CVE-2008-0485	High	February 5, 2008 2/5/08	<= 1.02rc2
CVE-2008-0486	High	February 5, 2008 2/5/08	== 1.02rc2
CVE-2007-4938	High	September 18, 2007 9/18/07	== 1.0_rc1
CVE-2007-2948	High	June 7, 2007 6/7/07	== 1.0_rc1
CVE-2007-1387	Medium	March 13, 2007 3/13/07	<= 1.0_rc1
CVE-2007-1246	High	March 3, 2007 3/3/07	<= 1.0_rc1
CVE-2006-6172	High	November 30, 2006 11/30/06	<= 1.0_rc1
CVE-2006-1502	Medium	March 30, 2006 3/30/06	<= 1.0_pre7try2
CVE-2006-0579	High	February 8, 2006 2/8/06	<= 1.0_pre7try2
CVE-2005-2718	High	August 29, 2005 8/29/05	<= 1.0_pre7
CVE-2005-1195	High	May 2, 2005 5/2/05	<= 1.0_pre6
CVE-2004-1187	High	January 10, 2005 1/10/05	== 0.90 == 0.90_pre == 0.90_rc == 0.90_rc4 == 0.91 == 0.92 == 0.92_cvs == 0.92.1 == 1.0_pre1 == 1.0_pre2 == 1.0_pre3 == 1.0_pre3try2 == 1.0_pre4 == 1.0_pre5 == 1.0_pre5try1 == 1.0_pre5try2 == head_cvs
CVE-2004-1188	High	January 10, 2005 1/10/05	== 0.90 == 0.90_pre == 0.90_rc == 0.90_rc4 == 0.91 == 0.92 == 0.92_cvs == 0.92.1 == 1.0_pre1 == 1.0_pre2 == 1.0_pre3 == 1.0_pre3try2 == 1.0_pre4 == 1.0_pre5 == 1.0_pre5try1 == 1.0_pre5try2 == head_cvs
CVE-2004-1285	High	January 10, 2005 1/10/05	== 0.92 == 1.0_pre2 == 0.90 == 1.0_pre1 == 0.92.1 == 1.0_pre3 == 1.0_pre5 == 0.91 == 1.0_pre5try1 == 1.0_pre3try2 == 1.0_pre4
CVE-2004-1310	High	January 10, 2005 1/10/05	== 1.0_pre5
CVE-2004-1311	High	January 10, 2005 1/10/05	== 1.0_pre5
CVE-2004-0433	High	August 18, 2004 8/18/04	== 1.0_pre3try2
CVE-2004-0659	High	August 6, 2004 8/6/04	== 0.92 == 1.0_pre2 == 0.90 == 1.0_pre1 == 0.90_rc == head_cvs == 0.92.1 == 1.0_pre3 == 0.92_cvs == 0.91 == 1.0_pre3try2 == 0.90_pre == 0.90_rc4 == 1.0_pre4
CVE-2004-0386	High	May 4, 2004 5/4/04	== 1.0_pre2 == 0.90 == 1.0_pre1 == 0.90_rc == 1.0_pre3 == 0.91 == 0.90_pre
CVE-2003-0835	High	November 17, 2003 11/17/03	== 0.90 == 1.0_pre1 == 0.90_rc == 0.91 == 0.90_pre == 0.90_rc4

mplayerhq / mplayer

19 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-38600	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38851	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38855	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38856	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38858	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38860	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38861	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38862	High	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38863	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38864	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38865	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38866	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-38853	Medium	September 15, 2022 9/15/22	== svn-r38374-13.0.1
CVE-2022-32317	Medium	July 14, 2022 7/14/22	== 1.5
CVE-2011-2162	High	May 20, 2011 5/20/11	== 1.0
CVE-2011-2160	High	May 20, 2011 5/20/11	*
CVE-2010-3908	Medium	May 20, 2011 5/20/11	*
CVE-2011-0722	Medium	May 20, 2011 5/20/11	*
CVE-2010-3429	Medium	September 30, 2010 9/30/10	<= 1.0 == 0.01 == 0.02 == 0.05 == 0.06 == 0.07 == 0.08 == 0.09-pre3 == 0.09 == 0.10-pre1 == 0.10-pre5 == 0.10-pre6 == 0.10 == 0.10-pre7 == 0.10-pre2 == 0.10-pre3 == 0.10-pre4 == 0.11-pre9 == 0.11-pre13 == 0.11-pre24 == 0.11-pre19 == 0.11-pre18 == 0.11-pre14 == 0.11-pre7 == 0.11-pre22 == 0.11-pre2 == 0.11-pre23 == 0.11-pre20 == 0.11-pre5 == 0.11-pre15 == 0.11-pre11 == 0.11-pre12 == 0.11-pre6 == 0.11-pre21 == 0.11-pre8 == 0.11-pre17 == 0.11-pre10 == 0.11-pre16 == 0.11-pre3 == 0.11-pre4 == 0.17_idegcounter == 0.17a_idegcounter == 0.18-pre4 == 0.18-pre3 == 0.18-pre1 == 0.18-pre2 == 0.18-pre5 == 0.50-pre3 == 0.50 == 0.50-pre2 == 0.50-pre1 == 0.60 == 0.60-pre1 == 0.60-pre2 == 0.90-rc3-pre3 == 0.90-rc2 == 0.90-rc1 == 0.90-rc3 == 0.90-pre1 == 0.90-pre2 == 0.90-pre8 == 0.90-rc3-pre1 == 0.90-pre5 == 0.90-rc5 == 0.90-pre6 == 0.90-rc3-pre2 == 0.90-pre3 == 0.90-pre9 == 0.90-pre7 == 0.90-rc4 == 0.90-pre10 == 0.90 == 0.90-pre4 == 0.91 == 0.92 == 0.92.1 == 0.93 == 1.0-pre5 == 1.0-pre6 == 1.0-pre5try2 == 1.0-pre3 == 1.0-pre7 == 1.0-rc2 == 1.0-pre4 == 1.0-rc1 == 1.0-pre7try2 == 1.0-pre8 == 1.0-pre3try2 == 1.0-pre1 == 1.0-pre2 == 1.0-pre6a

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