|
Vulnerability Report: Avaya Call Management System (CMS)
|
This vulnerability report for Avaya Call Management System (CMS) contains a complete overview of all Secunia advisories affecting it. You can use this vulnerability report to ensure that you are aware of all vulnerabilities, both patched and unpatched, affecting this product allowing you to take the necessary precautions.
If you have information about a new or an existing vulnerability in Avaya Call Management System (CMS) then you are more than welcome to contact us.
|
|
|
|
|
Vendor, Links, and Unpatched Vulnerabilities
| Vendor |
Avaya
|
|
|
Product Link
|
View Here (Link to external site)
|
|
|
Affected By
|
99 Secunia advisories
141 Vulnerabilities
|
|
|
Monitor Product
|
Receive alerts for this product
|
|
|
Unpatched
|
63% (62 of 99 Secunia advisories)
|
|
Most Critical Unpatched
The most severe unpatched Secunia advisory affecting Avaya Call Management System (CMS), with all vendor patches applied, is rated Highly critical .
|
|
|
|
|
|
33 Secunia Advisories in 2009
|
Secunia has issued a total of 33 Secunia advisories in 2009 for Avaya Call Management System (CMS). Currently, 88% (29 out of 33) are marked as unpatched with the most severe being rated Moderately critical 
More information about the specific Secunia advisories affecting Avaya Call Management System (CMS) can be found below. Each Secunia advisory is enclosed by a box highlighted with a color representing its current patch status. You can read the complete Secunia advisories for thorough descriptions of the issues covered and for solution suggestions by clicking either the Secunia advisory title or the "Read More" links available for each Secunia advisory.
|
|
|
|
|
|
Release Date: 2009-08-14 |
Secunia Advisory ID: SA36318 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and IR, which can be exploited by malicious users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-08-14 |
Secunia Advisory ID: SA36315 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: DoS
|
Where: From local network |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-08-14 |
Secunia Advisory ID: SA36272 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-06-30 |
Secunia Advisory ID: SA35637 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged two vulnerabilities in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-06-30 |
Secunia Advisory ID: SA35636 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users and potentially malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-06-10 |
Secunia Advisory ID: SA35414 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Security Bypass
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to bypass certain security restrictions. [Read More]
|
|
|
|
|
|
Release Date: 2009-06-10 |
Secunia Advisory ID: SA35386 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Exposure of sensitive information DoS System access
|
Where: From remote |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS, which can be exploited by malicious people to cause a DoS (Denial of Service), disclose potentially sensitive information, or potentially compromise an application using the libpng library. [Read More]
|
|
|
|
|
|
Release Date: 2009-05-28 |
Secunia Advisory ID: SA35191 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: System access
|
Where: From local network |
|
Short Description: Avaya has acknowledged two vulnerabilities in Avaya CMS, which can be exploited by malicious people to compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2009-05-25 |
Secunia Advisory ID: SA35206 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS System access
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to cause a DoS (Denial of Service) and potentially compromise an application using the affected library. [Read More]
|
|
|
|
|
|
Release Date: 2009-05-21 |
Secunia Advisory ID: SA35119 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-05-20 |
Secunia Advisory ID: SA35181 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-05-20 |
Secunia Advisory ID: SA35098 |
Solution Status: Vendor Workaround |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-04-21 |
Secunia Advisory ID: SA34814 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Exposure of sensitive information DoS System access
|
Where: From remote |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS, which can potentially be exploited by malicious people to disclose sensitive information, cause a DoS (Denial of Service), or compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2009-04-21 |
Secunia Advisory ID: SA34813 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to perform certain actions with escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2009-03-30 |
Secunia Advisory ID: SA34487 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-03-30 |
Secunia Advisory ID: SA34504 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-03-24 |
Secunia Advisory ID: SA34456 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-03-24 |
Secunia Advisory ID: SA34455 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-03-24 |
Secunia Advisory ID: SA34435 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Security Bypass
|
Where: From local network |
|
Short Description: Avaya has acknowledged a security issue in Avaya CMS, which can be exploited by malicious users to bypass certain security restrictions. [Read More]
|
|
|
|
|
|
Release Date: 2009-03-23 |
Secunia Advisory ID: SA34429 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Security Bypass
|
Where: From local network |
|
Short Description: Avaya has acknowledged a security issue in Avaya CMS, which can be exploited by malicious people to bypass certain security restrictions. [Read More]
|
|
|
|
|
|
Release Date: 2009-03-19 |
Secunia Advisory ID: SA34375 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Security Bypass Privilege escalation DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service), bypass certain security restrictions, and potentially gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2009-03-19 |
Secunia Advisory ID: SA34371 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-03-11 |
Secunia Advisory ID: SA34247 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS System access
|
Where: From remote |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS / IR, which can be exploited by malicious people to cause a DoS (Denial of Service) or potentially to compromise an application using the libxml2 library. [Read More]
|
|
|
|
|
|
Release Date: 2009-03-11 |
Secunia Advisory ID: SA34260 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2009-02-09 |
Secunia Advisory ID: SA33905 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Privilege escalation DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service) and potentially to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2009-02-09 |
Secunia Advisory ID: SA33904 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-02-09 |
Secunia Advisory ID: SA33903 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-02-09 |
Secunia Advisory ID: SA33882 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Spoofing
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to conduct spoofing attacks. [Read More]
|
|
|
|
|
|
Release Date: 2009-01-29 |
Secunia Advisory ID: SA33715 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS System access
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to cause a DoS (Denial of Service) or potentially compromise an application using the library. [Read More]
|
|
|
|
|
|
Release Date: 2009-01-29 |
Secunia Advisory ID: SA33708 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-01-29 |
Secunia Advisory ID: SA33702 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-01-29 |
Secunia Advisory ID: SA33705 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2009-01-22 |
Secunia Advisory ID: SA33628 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: From local network |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|