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,773

Total vulnerabilities in the database

Vulnerabilities for products matching "android"

Found 3 matching products. Filters apply to all results.

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

google / android

6504 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2015-3106	High	June 10, 2015 6/10/15	*
CVE-2015-3104	High	June 10, 2015 6/10/15	*
CVE-2015-3103	High	June 10, 2015 6/10/15	*
CVE-2015-3102	Medium	June 10, 2015 6/10/15	*
CVE-2015-3100	High	June 10, 2015 6/10/15	*
CVE-2015-3101	Low	June 10, 2015 6/10/15	*
CVE-2015-3099	Medium	June 10, 2015 6/10/15	*
CVE-2015-3098	Medium	June 10, 2015 6/10/15	*
CVE-2015-3096	Medium	June 10, 2015 6/10/15	*
CVE-2015-1474	High	February 16, 2015 2/16/15	<= 5.0
CVE-2014-9322	High	December 17, 2014 12/17/14	== 6.0 == 6.0.1
CVE-2014-8610	Low	December 15, 2014 12/15/14	== 2.2.3 == 2.0.1 == 1.0 == 3.2.6 == 4.2 == 1.6 == 2.1 == 4.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 2.3-rev1 == 4.4.3 == 2.3.6 == 4.0.4 == 4.3 == 4.0.1 == 2.3.3 == 3.0 == 2.0 == 4.2.1 == 2.3.1 == 2.3.5 == 1.5 == 3.1 == 4.0.3 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 4.0 == 4.4 == 4.4.1 == 2.3.7 == 2.2-rev1 == 1.1 <= 4.4.4 == 4.2.2 == 2.3.2 == 4.3.1 == 3.2.1 == 4.4.2 == 2.3 == 4.1.2
CVE-2014-8609	High	December 15, 2014 12/15/14	== 4.2 == 4.1 == 4.0.2 == 4.4.3 == 4.0.4 == 4.3 == 4.0.1 == 4.2.1 == 4.0.3 == 4.0 == 4.4 == 4.4.1 <= 4.4.4 == 4.2.2 == 4.3.1 == 4.4.2 == 4.1.2
CVE-2014-8507	High	December 15, 2014 12/15/14	== 2.2.3 == 2.0.1 == 1.0 == 3.2.6 == 4.2 == 1.6 == 2.1 == 4.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 2.3-rev1 == 4.4.3 == 2.3.6 == 4.0.4 == 4.3 == 4.0.1 == 2.3.3 == 3.0 == 2.0 == 4.2.1 == 2.3.1 == 2.3.5 == 1.5 == 3.1 == 4.0.3 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 4.0 == 4.4 == 4.4.1 == 2.3.7 == 2.2-rev1 == 1.1 <= 4.4.4 == 4.2.2 == 2.3.2 == 4.3.1 == 3.2.1 == 4.4.2 == 2.3 == 4.1.2
CVE-2014-7911	High	December 15, 2014 12/15/14	== 2.2.3 == 2.0.1 == 1.0 == 3.2.6 == 4.2 == 1.6 == 2.1 == 4.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 2.3-rev1 == 4.4.3 == 2.3.6 == 4.0.4 == 4.3 == 4.0.1 == 2.3.3 == 3.0 == 2.0 == 4.2.1 == 2.3.1 == 2.3.5 == 1.5 == 3.1 == 4.0.3 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 4.0 == 4.4 == 4.4.1 == 2.3.7 == 2.2-rev1 == 1.1 <= 4.4.4 == 4.2.2 == 2.3.2 == 4.3.1 == 3.2.1 == 4.4.2 == 2.3 == 4.1.2
CVE-2014-6060	Low	September 4, 2014 9/4/14	<= 4.4.3
CVE-2014-3100	Medium	July 2, 2014 7/2/14	== 4.3
CVE-2010-4832	Low	May 14, 2014 5/14/14	<= 2.1 == 2.0.1 == 1.0 == 1.6 == 2.0 == 1.5 == 1.1
CVE-2013-7373	High	April 29, 2014 4/29/14	== 2.2.3 == 2.0.1 == 1.0 == 3.2.6 == 4.2 == 1.6 == 2.1 == 4.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 2.3-rev1 <= 4.3.1 == 2.3.6 == 4.0.4 == 4.3 == 4.0.1 == 2.3.3 == 3.0 == 2.0 == 4.2.1 == 2.3.1 == 2.3.5 == 1.5 == 3.1 == 4.0.3 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 4.0 == 2.3.7 == 2.2-rev1 == 1.1 == 4.2.2 == 2.3.2 == 3.2.1 == 2.3 == 4.1.2
CVE-2013-7372	Medium	April 29, 2014 4/29/14	<= 4.3.1 == 4.0 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.4 == 4.1 == 4.1.2 == 4.2 == 4.2.1 == 4.2.2 == 4.3
CVE-2013-6770	High	March 31, 2014 3/31/14	== 4.4
CVE-2013-4710	High	March 3, 2014 3/3/14	== 3.2.6 == 4.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 4.0.4 == 4.0.1 == 3.0 == 3.1 == 4.0.3 == 4.0 == 3.2.1 == 4.1.2
CVE-2014-1939	High	March 3, 2014 3/3/14	<= 4.3.1 == 4.0 == 4.0.1 == 4.0.2 == 4.0.3 == 4.0.4 == 4.1 == 4.1.2 == 4.2 == 4.2.1 == 4.2.2 == 4.3
CVE-2013-6271	High	December 14, 2013 12/14/13	== 4.2 == 4.1 == 4.0.2 == 4.0.4 == 4.3 == 4.0.1 == 4.2.1 == 4.0.3 == 4.0 == 4.2.2 == 4.1.2
CVE-2013-4777	Medium	September 25, 2013 9/25/13	== 2.3.7
CVE-2013-5933	Medium	September 25, 2013 9/25/13	== 2.3.7
CVE-2013-4787	High	July 9, 2013 7/9/13	== 2.2.3 == 2.0.1 == 3.2.6 == 4.2 == 1.6 == 2.1 == 4.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 2.3-rev1 == 2.3.6 == 4.0.4 == 4.0.1 == 2.3.3 == 3.0 == 2.0 == 2.3.1 == 2.3.5 == 3.1 == 4.0.3 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 4.0 == 2.3.7 == 2.2-rev1 == 2.3.2 == 3.2.1 == 2.3 == 4.1.2
CVE-2013-3666	High	May 29, 2013 5/29/13	== 4.1.2
CVE-2011-1350	High	February 5, 2013 2/5/13	== 2.2.3 == 2.0.1 == 1.0 == 1.6 == 2.1 == 2.3.3 == 2.0 == 2.3.1 <= 2.3.5 == 1.5 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 1.1 == 2.3.2 == 2.3
CVE-2011-1352	Medium	February 5, 2013 2/5/13	== 2.2.3 == 2.0.1 == 1.0 == 1.6 == 2.1 == 2.3.3 == 2.0 == 2.3.1 <= 2.3.5 == 1.5 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 1.1 == 2.3.2 == 2.3
CVE-2012-6301	Medium	December 10, 2012 12/10/12	== 4.0.3
CVE-2012-4220	Medium	November 30, 2012 11/30/12	== 3.2.6 == 4.2 == 4.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 2.3-rev1 == 2.3.6 == 4.0.4 == 4.0.1 == 2.3.3 == 3.0 == 2.3.1 == 2.3.5 == 3.1 == 4.0.3 == 2.3.4 == 4.0 == 2.3.7 == 2.3.2 == 3.2.1 == 2.3
CVE-2012-4221	Medium	November 30, 2012 11/30/12	== 3.2.6 == 4.2 == 4.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 2.3-rev1 == 2.3.6 == 4.0.4 == 4.0.1 == 2.3.3 == 3.0 == 2.3.1 == 2.3.5 == 3.1 == 4.0.3 == 2.3.4 == 4.0 == 2.3.7 == 2.3.2 == 3.2.1 == 2.3
CVE-2012-4222	Low	November 30, 2012 11/30/12	== 3.2.6 == 4.2 == 4.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 2.3-rev1 == 2.3.6 == 4.0.4 == 4.0.1 == 2.3.3 == 3.0 == 2.3.1 == 2.3.5 == 3.1 == 4.0.3 == 2.3.4 == 4.0 == 2.3.7 == 2.3.2 == 3.2.1 == 2.3
CVE-2011-3918	High	October 7, 2012 10/7/12	== 2.2.3 == 2.0.1 == 1.0 == 3.2.6 == 1.6 == 2.1 == 3.2.4 == 3.2 == 3.2.2 == 4.0.2 == 2.3-rev1 == 2.3.6 == 4.0.1 == 2.3.3 == 3.0 == 2.0 == 2.3.1 == 2.3.5 == 1.5 == 3.1 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 4.0 == 2.3.7 == 2.2-rev1 == 1.1 == 2.3.2 == 3.2.1 == 2.3 <= 4.0.3
CVE-2012-3979	Medium	August 29, 2012 8/29/12	*
CVE-2011-3874	High	January 27, 2012 1/27/12	== 2.3-rev1 == 2.3.6 == 2.3.3 == 2.3.1 == 2.3.5 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 2.2-rev1 == 2.3.2 == 2.3
CVE-2011-4276	Low	January 25, 2012 1/25/12	== 2.3.3 == 2.3.5 == 2.3.4 == 2.3
CVE-2011-3881	Low	October 25, 2011 10/25/11	< 4.4
CVE-2011-3975	Low	October 3, 2011 10/3/11	== 2.3.4
CVE-2011-2357	Low	August 12, 2011 8/12/11	== 3.1 == 2.3.4
CVE-2008-7298	Medium	August 9, 2011 8/9/11	*
CVE-2011-2344	High	July 8, 2011 7/8/11	== 2.1 == 2.3-rev1 == 2.3.3 == 3.0 == 2.2.1 == 2.2.2 == 2.2 == 2.3.4 == 2.2-rev1
CVE-2010-4804	Low	June 9, 2011 6/9/11	== 1.6 == 2.1 == 2.3-rev1 == 1.5 == 2.2.1 == 2.2.2 == 2.2 == 2.2-rev1 <= 2.3.3
CVE-2011-1823	High	June 9, 2011 6/9/11	== 3.0 >= 2.0 < 2.3.4
CVE-2011-0419	Low	May 16, 2011 5/16/11	*
CVE-2011-1149	High	April 21, 2011 4/21/11	== 1.6 == 2.1 == 1.5 == 2.2.1 == 2.2-rev1 <= 2.2.2
CVE-2011-0680	Medium	January 31, 2011 1/31/11	== 1.6 == 2.1 == 2.3-rev1 == 1.5 == 2.2-rev1 <= 2.2.1
CVE-2010-1807	High	September 10, 2010 9/10/10	<= 2.1 == 1.0 == 1.1 == 1.5 == 1.6 == 2.0
CVE-2009-3698	Low	October 14, 2009 10/14/09	<= 1.5

Showing vulnerabilities for 3 products matching "android". 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.