Vulnerability Database

326,214

Total vulnerabilities in the database

Vulnerabilities for products matching "adaptive_security_appliance"

Found 1 matching product.

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

cisco / adaptive_security_appliance

62 vulnerabilities found
Title Severity Exploit Date Affected Version
High March 23, 2023 3/23/23
< 9.12.1
Medium April 21, 2022 4/21/22
<= 9.16.3
High January 11, 2022 1/11/22
<= 9.7
Medium October 27, 2021 10/27/21
< 9.8.4.40
Low October 27, 2021 10/27/21
< 9.8.4.40
Low October 27, 2021 10/27/21
< 9.8.4.40
High October 27, 2021 10/27/21
< 9.8.4.40
High October 27, 2021 10/27/21
< 9.8.4.40
High October 27, 2021 10/27/21
< 9.8.4.40
Medium October 21, 2020 10/21/20
< 9.6.4.45
Medium October 21, 2020 10/21/20
< 9.6
High October 21, 2020 10/21/20
< 9.6
High October 21, 2020 10/21/20
< 9.12.4.3
Medium October 21, 2020 10/21/20
< 9.6.4.43
Low October 21, 2020 10/21/20
< 9.6.4.35
High October 21, 2020 10/21/20
< 9.6.4.45
High October 21, 2020 10/21/20
< 9.6
High October 21, 2020 10/21/20
< 9.6.4.45
High October 21, 2020 10/21/20
< 9.6.4.45
High September 23, 2020 9/23/20
< 9.6.4.36
High May 6, 2020 5/6/20
< 9.6.4.36
High May 6, 2020 5/6/20
< 9.6.4.36
High May 6, 2020 5/6/20
< 9.6.4.34
Low October 2, 2019 10/2/19
< 9.6.4.30
Medium October 2, 2019 10/2/19
< 9.6.4.31
High October 2, 2019 10/2/19
< 9.6.4.31
High October 2, 2019 10/2/19
< 9.6.4.34
High October 2, 2019 10/2/19
< 9.6.4.34
High October 2, 2019 10/2/19
< 9.4.4.37
Low January 8, 2014 1/8/14
*
Low January 8, 2014 1/8/14
*
High December 2, 2013 12/2/13
*
Low August 30, 2013 8/30/13
*
Low July 25, 2013 7/25/13
*
High June 26, 2013 6/26/13
== 9.1.1.7
== 9.1.2.5
== 9.1.1.4
== 9.1.1
== 9.1.2.1
== 9.1.2.11
== 9.1.2.7
== 9.1.1.3
== 9.1.2.6
== 9.1.1.6
== 9.1.2.4
== 9.1.1.8
== 9.1.1.1
== 9.1.2.8
== 9.1.2.9
== 9.1.2
== 9.1.2.3
== 9.1.2.10
== 9.1.1.5
== 9.1.1.2
== 9.1.2.2
Low April 18, 2013 4/18/13
*
Medium April 18, 2013 4/18/13
*
Medium April 16, 2013 4/16/13
*
High April 11, 2013 4/11/13
*
High April 11, 2013 4/11/13
*
Medium February 25, 2013 2/25/13
*
Medium January 18, 2013 1/18/13
*
Medium January 18, 2013 1/18/13
*
High February 25, 2011 2/25/11
== 8.1(1)
== 8.1(2)
High February 25, 2011 2/25/11
== 8.0(2)
== 8.0(3)
== 8.0(4)
== 8.0(5)
== 8.1(1)
== 8.1(2)
== 8.2
== 8.2(1)
== 8.2(2)
== 8.3
High February 25, 2011 2/25/11
== 8.0(2)
== 8.0(3)
== 8.0(4)
== 8.0(5)
== 8.1(1)
== 8.1(2)
== 8.2
== 8.2(1)
== 8.2(2)
== 8.3
High August 9, 2010 8/9/10
== 7.2(3)
== 7.2(4)
== 7.2(5)
== 8.0(2)
== 8.0(3)
== 8.0(4)
== 8.0(5)
== 8.1(1)
== 8.1(2)
== 8.2
== 8.2(1)
== 8.2(2)
== 8.3
High August 9, 2010 8/9/10
== 7.2(3)
== 7.2(4)
== 7.2(5)
== 8.0(2)
== 8.0(3)
== 8.0(4)
== 8.0(5)
== 8.1(1)
== 8.1(2)
== 8.2
== 8.2(1)
== 8.2(2)
== 8.3
High August 9, 2010 8/9/10
== 8.0(2)
== 8.0(3)
== 8.0(4)
== 8.0(5)
== 8.1(1)
== 8.1(2)
== 8.2
== 8.2(1)
== 8.2(2)
High August 9, 2010 8/9/10
== 7.0.1
== 7.0.2
== 7.0.3
== 7.0.4
== 7.0.5
== 7.0.6
== 7.0.7
== 7.0.8
== 7.1.1
== 7.1.2
== 7.2(3)
== 7.2(4)
== 7.2(5)
== 8.0(2)
== 8.0(3)
== 8.0(4)
== 8.0(5)
== 8.1(1)
== 8.1(2)
== 8.2
== 8.2(1)
== 8.2(2)
== 8.3

Frequently Asked Questions

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.