Vulnerability Database

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "unified_computing_system"

Found 1 matching product.

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

cisco / unified_computing_system

64 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium November 18, 2024 11/18/24
== 3.2(1d)
== 3.2(2b)
== 3.2(2c)
== 3.2(2d)
== 3.2(2e)
== 3.2(2f)
== 3.2(3a)
== 3.2(3b)
== 3.2(3d)
== 3.2(3e)
== 3.2(3g)
== 3.2(3h)
== 3.2(3i)
== 3.2(3j)
== 3.2(3k)
== 3.2(3l)
== 3.2(3n)
== 3.2(3o)
== 3.2(3p)
== 4.0(1a)
== 4.0(1b)
== 4.0(1c)
== 4.0(1d)
== 4.0(2a)
== 4.0(2b)
== 4.0(2d)
== 4.0(2e)
== 4.0(4a)
== 4.0(4b)
== 4.0(4c)
== 4.0(4d)
== 4.0(4e)
== 4.0(4f)
== 4.0(4g)
== 4.0(4h)
== 4.0(4i)
== 4.1(1a)
== 4.1(1b)
== 4.1(1c)
== 4.1(1d)
== 4.1(1e)
== 4.1(2a)
Medium October 2, 2024 10/2/24
== 4.1(2a)
== 4.1(2b)
== 4.1(3a)
== 4.1(3b)
== 4.1(2c)
== 4.1(4a)
== 4.2(1m)
== 4.2(1l)
== 4.1(3h)
== 4.2(1k)
== 4.2(1i)
== 4.1(3f)
== 4.2(1f)
== 4.1(3e)
== 4.2(1d)
== 4.2(1c)
== 4.1(3d)
== 4.1(3c)
== 4.2(3b)
== 4.1(3k)
== 4.2(2e)
== 4.2(3d)
== 4.2(3e)
== 4.2(3g)
== 4.1(3l)
== 4.3(2b)
== 4.2(3h)
== 4.2(3i)
== 4.3(2c)
== 4.1(3m)
== 4.3(2e)
== 4.3(3a)
== 4.2(3j)
== 4.3(3c)
== 4.3(4a)
== 4.2(3k)
== 4.2(2d)
== 4.2(2c)
== 4.1(3j)
== 4.2(1n)
== 4.2(2a)
== 4.1(3i)
== 4.3(4b)
Medium February 29, 2024 2/29/24
== 3.1(1e)
== 3.1(1g)
== 3.1(1h)
== 3.1(1k)
== 3.1(1l)
== 3.1(2b)
== 3.1(2c)
== 3.1(2d)
== 3.1(2e)
== 3.1(2f)
== 3.1(2g)
== 3.1(2h)
== 3.1(3a)
== 3.1(3b)
== 3.1(3c)
== 3.1(3d)
== 3.1(3e)
== 3.1(3f)
== 3.1(3h)
== 3.1(3j)
== 3.1(3k)
== 3.1(3l)
== 3.2(1d)
== 3.2(2b)
== 3.2(2c)
== 3.2(2d)
== 3.2(2e)
== 3.2(2f)
== 3.2(3a)
== 3.2(3b)
== 3.2(3d)
== 3.2(3e)
== 3.2(3g)
== 3.2(3h)
== 3.2(3i)
== 3.2(3j)
== 3.2(3k)
== 3.2(3l)
== 3.2(3n)
== 3.2(3o)
== 3.2(3p)
== 4.0(1a)
== 4.0(1b)
== 4.0(1c)
== 4.0(1d)
== 4.0(2a)
== 4.0(2b)
== 4.0(2d)
== 4.0(2e)
== 4.0(4a)
== 4.0(4b)
== 4.0(4c)
== 4.0(4d)
== 4.0(4e)
== 4.0(4f)
== 4.0(4g)
== 4.0(4h)
== 4.0(4i)
== 4.0(4k)
== 4.0(4l)
== 4.0(4m)
== 4.0(4n)
== 4.0(4o)
== 4.1(1a)
== 4.1(1b)
== 4.1(1c)
== 4.1(1d)
== 4.1(1e)
== 4.1(2a)
== 4.1(2b)
== 4.1(2c)
== 4.1(3a)
== 4.1(3b)
== 4.1(3c)
== 4.1(3d)
== 4.1(3e)
== 4.1(3f)
== 4.1(3h)
== 4.1(3i)
== 4.1(3j)
== 4.1(3k)
== 4.1(3l)
== 4.2(1c)
== 4.2(1d)
== 4.2(1f)
== 4.2(1i)
== 4.2(1k)
== 4.2(1l)
== 4.2(1m)
== 4.2(1n)
== 4.2(2a)
== 4.2(2c)
== 4.2(2d)
== 4.2(2e)
== 4.2(3b)
== 4.2(3d)
== 4.2(3e)
== 4.2(3g)
== 4.2(3h)
== 4.2(3i)
Critical December 10, 2021 12/10/21
== 006.008(001.000)
Medium October 21, 2021 10/21/21
< 4.1\(2g\)
>= 4.2 < 4.2\(1b\)
< 4.1\(3e\)
Low August 25, 2021 8/25/21
>= 4.0 < 4.0\(4m\)
>= 4.1 < 4.1\(3e\)
Medium August 25, 2021 8/25/21
< 4.0\(4m\)
>= 4.1 < 4.1\(3d\)
High February 24, 2021 2/24/21
< 4.0\(4i\)
>= 4.1 < 4.1\(2c\)
High February 24, 2021 2/24/21
>= 4.0 < 4.0\(4k\)
>= 4.1 < 4.1\(1e\)
Medium September 23, 2020 9/23/20
== 3.2(3h)c
High August 30, 2019 8/30/19
== 3.2(3b)a
== 4.0(1a)a
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High August 21, 2019 8/21/19
== 4.0(1c)hs3
High June 20, 2019 6/20/19
== 4.0(1c)hs3
Medium June 20, 2019 6/20/19
== 4.0(1c)hs3
Medium June 20, 2019 6/20/19
== 4.0(1c)hs3
Medium June 20, 2019 6/20/19
== 4.0(1c)hs3
Low June 20, 2019 6/20/19
== 4.0(1c)hs3
Medium June 20, 2019 6/20/19
== 4.0(1c)hs3
Medium June 20, 2019 6/20/19
== 4.0(1c)hs3
Medium April 18, 2019 4/18/19
< 4.0\(2a\)
High October 5, 2018 10/5/18
== 2.0_base
== 3.1(3)
== 3.0(3a)
High October 5, 2018 10/5/18
== 2.0_base
== 3.1(3)
== 3.0(3a)
High June 7, 2018 6/7/18
== 5.5(203)
== 7.0(0)bz(0.46)
== 9.0(100.20)b
== 9.1(1.13)
== 9.9(0.902)
Low November 30, 2017 11/30/17
== 7.0(0)hsk(0.357)
High November 30, 2017 11/30/17
== 7.0(0)hsk(0.357)
Low November 30, 2017 11/30/17
== 7.0(0)hsk(0.357)
Low November 30, 2017 11/30/17
== 7.0(0)hsk(0.357)
High November 30, 2017 11/30/17
== 7.0(0)hsk(0.357)
Low November 30, 2017 11/30/17
== 7.0(0)hsk(0.357)
Low November 30, 2017 11/30/17
== 7.0(0)hsk(0.357)
Low November 30, 2017 11/30/17
== 7.0(0)hsk(0.357)
High November 30, 2017 11/30/17
== 7.0(0)hsk(0.357)
High September 21, 2017 9/21/17
== 1.5(1c)
Medium May 22, 2017 5/22/17
== 3.0(0.234)
High April 7, 2017 4/7/17
== 3.1(1k)a
High April 7, 2017 4/7/17
== 3.1(1k)a
High April 7, 2017 4/7/17
== 3.1(1k)a
Low April 7, 2017 4/7/17
== 3.1(1k)a
Low April 7, 2017 4/7/17
== 3.1(1k)a

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.