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.

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "adobe_air"

Found 1 matching product.

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

adobe / adobe_air

1884 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2012-4171	Medium	August 31, 2012 8/31/12	<= 3.3.0.3670
CVE-2012-0772	High	March 28, 2012 3/28/12	<= 3.1.0.488 == 1.0 == 1.0.1 == 1.1 == 1.5 == 1.5.1 == 1.5.2 == 1.5.3 == 1.5.3.9120 == 2.0.2 == 2.0.3 == 2.0.3.13070 == 2.0.4 == 2.6 == 2.7 == 2.7.0.1948 == 2.7.0.1953 == 2.7.1 == 2.7.1.19610 == 3.0.0.408 == 3.1.0.485
CVE-2012-0773	High	March 28, 2012 3/28/12	< 3.2.0.2070
CVE-2011-2445	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2450	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2451	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2452	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2453	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2454	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2455	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2456	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2457	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2458	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2459	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2460	High	November 11, 2011 11/11/11	>= 3.0 < 3.1.0.4880
CVE-2011-2424	High	August 15, 2011 8/15/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6 <= 2.7.1 == 2.7
CVE-2011-2416	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2417	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2425	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2135	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2136	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2138	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2139	Medium	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2140	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2414	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2415	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2130	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2134	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-2137	High	August 10, 2011 8/10/11	<= 2.7 == 1.0 == 1.1 == 1.5 == 1.5.2 == 1.5.3 == 2.0.2 == 2.0.3 == 2.0.4 == 2.6
CVE-2011-0611	High	April 13, 2011 4/13/11	< 2.6.19140
CVE-2010-2213	High	August 11, 2010 8/11/10	== 1.0 == 1.5 * == 1.5.1 == 1.5.3 == 1.5.3.9120 == 1.0.1
CVE-2010-2214	High	August 11, 2010 8/11/10	== 1.0 == 1.5 * == 1.5.1 == 1.5.3 == 1.5.3.9120 == 1.0.1
CVE-2010-2215	Low	August 11, 2010 8/11/10	== 1.0 == 1.5 * == 1.5.1 == 1.5.3 == 1.5.3.9120 == 1.0.1
CVE-2010-2216	High	August 11, 2010 8/11/10	== 1.0 == 1.5 * == 1.5.1 == 1.5.3 == 1.5.3.9120 == 1.0.1
CVE-2010-0209	High	August 11, 2010 8/11/10	== 1.0 == 1.5 * == 1.5.1 == 1.5.3 == 1.5.3.9120 == 1.0.1
CVE-2010-0186	Medium	February 15, 2010 2/15/10	== 1.0 == 1.5.1 <= 1.5.3.9120 == 1.5.3 == 1.5.2 == 1.1
CVE-2010-0187	Low	February 15, 2010 2/15/10	== 1.0 == 1.5.1 <= 1.5.3.9120 == 1.5.3 == 1.5.2 == 1.1
CVE-2009-3794	High	December 10, 2009 12/10/09	== 1.0 == 1.5.1 <= 1.5.2 == 1.0.1 == 1.1
CVE-2009-3796	High	December 10, 2009 12/10/09	== 1.0 == 1.5.1 <= 1.5.2 == 1.0.1 == 1.1
CVE-2009-3797	High	December 10, 2009 12/10/09	== 1.0 == 1.5.1 <= 1.5.2 == 1.0.1 == 1.1
CVE-2009-3798	High	December 10, 2009 12/10/09	== 1.0 == 1.5.1 <= 1.5.2 == 1.0.1 == 1.1
CVE-2009-3799	High	December 10, 2009 12/10/09	== 1.0 == 1.5.1 <= 1.5.2 == 1.0.1 == 1.1
CVE-2009-3800	High	December 10, 2009 12/10/09	== 1.0 == 1.5.1 <= 1.5.2 == 1.0.1 == 1.1
CVE-2009-3951	High	December 10, 2009 12/10/09	<= 1.5.2 == 1.0 == 1.0.1 == 1.1 == 1.5.1
CVE-2008-5108	Medium	November 17, 2008 11/17/08	== 1.0 <= 1.1
CVE-2007-3640	Low	July 10, 2007 7/10/07	*

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.