Vulnerability Database

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "unified_communications_manager"

Found 1 matching product.

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

cisco / unified_communications_manager

3007 vulnerabilities found
Title Severity Exploit Date Affected Version
High March 5, 2010 3/5/10
== 7.1
== 8.0
== 7.0(1)
== 7.0
== 7.0(2)
High March 5, 2010 3/5/10
== 6.1(2)
== 6.1.0
== 6.0(1)
== 6.1(2)su1a
== 6.1(4)
== 7.1
== 6.1
== 6.1(3)
== 6.1(1)
== 8.0
== 7.0(1)
== 6.1(1b)
== 6.0(1a)
== 7.0
== 6.1(2)su1
== 6.0
== 6.1(1a)
== 7.0(2)
High March 5, 2010 3/5/10
== 4.2_1
== 4.1.2
== 4.1-(3)sr5b
== 6.1(2)
== 6.1.0
== 4.2.3sr2
== 6.0(1)
== 4.2_2
== 4.1.1
== 4.3_1
== 4.1(3)sr1
== 6.1(2)su1a
== 4.2(3)sr2b
== 4.2.3_sr3
== 6.1-(1a)
== 7.1
== 4.1-(3)sr5
== 4.1-(3)sr5c
== 4.2.3sr1
== 4.1(3)sr2
== 4.3(2)sr1
== 4.1(3)
== 6.1
== 4.2
== 4.3
== 4.2.3
== 4.1(3)sr4
== 4.2.1
== 4.1.3
== 4.1-(3)sr.5
== 4.3-4.3(1)sr.1
== 6.1(1)
== 8.0
== 4.2-4.2_(3)sr2b
== 4.2_3sr1
== 4.2-4.2(3)sr.2
== 4.2(3)sr1
== 4.3(1)sr.1
== 4.2-4.2_(3)sr3
== 7.0(1)
== 4.2(3)sr4
== 4.2.2
== 4.3(1)
== 4.1(3)sr3
== 6.1(1b)
== 4.1
== 6.0(1a)
== 4.2_3
== 7.0
== 4.1-(3)sr4
== 4.3.1
== 4.3(2)
== 6.1(2)su1
== 6.0
== 4.2(3)sr3
== 4.2.3sr2b
== 6.1(1a)
== 7.0(2)
High September 28, 2009 9/28/09
== 5.1(3e)
== 5.1(3c)
== 6.1(2)
== 5.1(2a)
== 5.1(1b)
== 5.1(1c)
== 6.1(2)su1a
== 5.1(2)
== 7.1
== 6.1(3)
== 6.1(1)
== 5.1(3d)
== 7.0(1)
== 6.1(1b)
== 5.1(3)
== 6.1(2)su1
== 5.1(3a)
== 6.1(1a)
== 7.0(2)
High August 27, 2009 8/27/09
>= 6.1\(1\) < 6.1\(4\)
>= 5.0 < 5.1\(3g\)
>= 7.1 < 7.1\(2\)
>= 7.0 < 7.0\(2\)
High August 27, 2009 8/27/09
>= 6.1\(1\) < 6.1\(4\)
>= 5.0 < 5.1\(3g\)
>= 7.1 < 7.1\(2\)
>= 7.0 < 7.0\(2a\)su1
High August 27, 2009 8/27/09
>= 7.1 < 7.1\(2a\)su1
>= 6.0 < 6.1\(4\)
>= 7.0 < 7.0\(2a\)su1
>= 4.0 < 5.1\(3g\)
High August 27, 2009 8/27/09
< 6.1\(1\)
High August 27, 2009 8/27/09
>= 6.1\(1\) < 6.1\(4\)
>= 5.0 < 5.1\(3g\)
>= 7.1 < 7.1\(2\)
High March 12, 2009 3/12/09
== 5.1(3c)
== 6.1(2)
== 5.1(2a)
== 6.0(1)
== 5.1(2)
== 4.2(3)sr2b
== 5.0
== 4.3(2)sr1
== 5.1(2b)
== 6.1
== 4.2
== 4.3
== 6.1(3)
== 6.1(1)
== 5.1(3d)
== 4.2(3)sr1
== 4.3(1)sr.1
== 7.0(1)
== 4.2(3)sr4
== 5.1(3)
== 4.1
== 6.0(1a)
== 5.1(1)
== 7.0
== 4.3(2)
== 6.1(2)su1
== 5.1(3a)
== 6.0
== 4.2(3)sr3
== 6.1(1a)
Low January 22, 2009 1/22/09
== 5.0_4
== 5.1(3c)
== 6.1(2)
== 6.1.0
== 5.1-(1)
== 5.1_3a
== 5.0_4a
== 5.1(2)
== 5.1-5.1(1)
== 5.0
== 6.1-(1a)
== 5.1-(2)
== 5.0_1
== 6.1
== 5.1-(2a)
== 5.1_2a
== 5.0_4a_su1
== 5.1-5.1_(2a)
== 6.1_1a
== 5.1.2
== 5.1-(3a)
== 5.1_2b
== 5.0_3a
== 5.1_(2a)
== 6.0-(1a)
== 5.0_3
== 5.1(1)
== 6.0-(1)
== 5.0_2
== 5.1_2
== 6.0_1
== 5.1-(2b)
== 6.0
== 5.1
== 6.0_1a
== 5.1_1
High September 26, 2008 9/26/08
== 5.0
== 6.1
== 4.1
== 5.1
High September 26, 2008 9/26/08
== 5.0
== 6.1
== 4.1
== 5.1
High June 26, 2008 6/26/08
>= 5.0 < 5.1\(3c\)
>= 6.0 < 6.1\(2\)
Medium June 26, 2008 6/26/08
>= 4.3 < 4.3\(2\)sr1
>= 5.0 < 5.1\(3c\)
>= 6.0 < 6.1\(2\)
>= 4.2 < 4.2\(3\)sr4
Medium June 26, 2008 6/26/08
== 6.1
== 5.1
High May 16, 2008 5/16/08
== 5.1-(1)
== 6.1-(1a)
== 5.1-(2)
== 6.1
== 5.1-(2a)
== 4.2
== 4.3
== 5.1-(3a)
== 6.0-(1a)
== 4.1
== 6.0-(1)
== 5.1-(2b)
== 6.0
High May 16, 2008 5/16/08
>= 5.0 < 5.1\(3\)
>= 6.0 < 6.1\(1\)
High May 16, 2008 5/16/08
== 4.2_3_sr3
== 5.1_3a
== 4.3_1_sr1
== 6.1
== 5.1_2a
== 4.3
== 4.2_3_sr2b
== 6.1_1a
== 4.2_3_sr2
== 5.1_2b
== 5.1_2
== 6.0_1
== 6.0
== 6.0_1a
== 5.1_1
High May 16, 2008 5/16/08
== 4.1-(3)sr5b
== 5.1-(1)
== 6.1-(1a)
== 5.1-(2)
== 4.1-(3)sr5
== 4.1-(3)sr5c
== 6.1
== 5.1-(2a)
== 4.3
== 4.1-(3)sr.5
== 4.3-4.3(1)sr.1
== 5.1-(3a)
== 4.2-4.2_(3)sr2b
== 4.2-4.2(3)sr.2
== 4.2-4.2_(3)sr3
== 6.0-(1a)
== 4.1
== 6.0-(1)
== 4.1-(3)sr4
== 5.1-(2b)
== 6.0
High May 16, 2008 5/16/08
== 4.1-(3)sr5b
== 5.1-(1)
== 6.1-(1a)
== 5.1-(2)
== 4.1-(3)sr5
== 4.1-(3)sr5c
== 6.1
== 5.1-(2a)
== 4.3
== 4.1-(3)sr.5
== 4.3-4.3(1)sr.1
== 4.2-4.2_(3)sr2b
== 4.2-4.2(3)sr.2
== 4.2-4.2_(3)sr3
== 4.1
== 4.1-(3)sr4
== 5.1-(2b)
== 6.0
High May 16, 2008 5/16/08
>= 4.1 < 4.1\(3\)sr6
>= 4.2 < 4.2\(3\)sr3
>= 4.3 < 4.3\(2\)
>= 5.0 < 5.1\(3\)
>= 6.0 < 6.1\(1\)
High May 16, 2008 5/16/08
>= 4.3 < 4.3\(2\)
>= 5.0 < 5.1\(3\)
>= 6.0 < 6.1\(1\)
>= 4.1 < 4.1\(3\)sr7
>= 4.2 < 4.2\(3\)sr4
High April 4, 2008 4/4/08
== 5.0
== 6.1
== 6.0
== 5.1
Medium February 14, 2008 2/14/08
== 5.0_4
== 5.0_4a
== 5.0
== 5.0_1
== 6.1
== 5.0_4a_su1
== 5.0_3a
== 5.0_3
== 5.0_2
== 6.0_1
== 6.0
High January 17, 2008 1/17/08
== 4.2.3sr2
== 4.2
== 4.3
== 4.2.3sr2b
High October 18, 2007 10/18/07
<= 5.1\(2\)
High October 18, 2007 10/18/07
<= 5.1\(2\)
Low August 31, 2007 8/31/07
== 4.2.3sr2
== 4.2.3sr2b
High August 31, 2007 8/31/07
== 3.3(5)
== 4.1(3)sr1
== 4.2.3sr1
== 4.1(3)sr2
== 4.1(3)
== 4.2
== 4.3
== 4.2.3
== 4.1(3)sr4
== 4.2.1
== 3.3(5)sr2a
== 4.2.2
== 4.3(1)
== 4.1(3)sr3
== 3.3(5)sr1
Medium August 9, 2007 8/9/07
== 5.0
== 5.1
== 6.0
High July 15, 2007 7/15/07
>= 4.3 <= 4.3\(1\)
High July 15, 2007 7/15/07
== 5.1(2)
== 5.0
== 5.1(1)
Medium July 15, 2007 7/15/07
== 5.1(2)
== 5.0
== 5.1(1)
High July 15, 2007 7/15/07
>= 4.3 <= 4.3\(1\)
>= 5.1 <= 5.1\(1\)

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.