|
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 .
|
|
|
|
|
|
99 Secunia Advisories in 2003-2009
|
Secunia has issued a total of 99 Secunia advisories in 2003-2009 for Avaya Call Management System (CMS). Currently, 63% (62 out of 99) are marked as unpatched with the most severe being rated Highly 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: 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-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-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: 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-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-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: 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-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-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]
|
|
|
|
|
|
Release Date: 2008-12-26 |
Secunia Advisory ID: SA33308 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Exposure of sensitive information
|
Where: From local network |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which potentially can be exploited by malicious people to disclose sensitive information. [Read More]
|
|
|
|
|
|
Release Date: 2008-12-26 |
Secunia Advisory ID: SA33325 |
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]
|
|
|
|
|
|
Release Date: 2008-12-26 |
Secunia Advisory ID: SA33313 |
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: 2008-12-22 |
Secunia Advisory ID: SA33242 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Exposure of sensitive information
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in various Avaya products, which can be exploited by malicious people to disclose sensitive information. [Read More]
|
|
|
|
|
|
Release Date: 2008-12-16 |
Secunia Advisory ID: SA33187 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Security Bypass System access
|
Where: From remote |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS, which can be exploited by malicious people to bypass certain security restrictions or compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2008-11-21 |
Secunia Advisory ID: SA32812 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: System access
|
Where: From local network |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2008-10-03 |
Secunia Advisory ID: SA32125 |
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: 2008-10-03 |
Secunia Advisory ID: SA31907 |
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: 2008-08-20 |
Secunia Advisory ID: SA31536 |
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) or to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2008-08-20 |
Secunia Advisory ID: SA31535 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: System access
|
Where: From remote |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS, which can be exploited by malicious people to compromise a user's system. [Read More]
|
|
|
|
|
|
Release Date: 2008-08-20 |
Secunia Advisory ID: SA31501 |
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: 2008-07-28 |
Secunia Advisory ID: SA31269 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Security Bypass
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to bypass certain security restrictions. [Read More]
|
|
|
|
|
|
Release Date: 2008-07-01 |
Secunia Advisory ID: SA30843 |
Solution Status: Vendor Workaround |
|
Criticality:
 |
Impact: Exposure of sensitive information Privilege escalation DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS / IR, which can be exploited by malicious, local users to cause a DoS (Denial of Service), disclose potentially sensitive information, or to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2008-06-16 |
Secunia Advisory ID: SA30718 |
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 to potentially compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2008-06-05 |
Secunia Advisory ID: SA30542 |
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: 2008-06-02 |
Secunia Advisory ID: SA30473 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: System access
|
Where: From local network |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS, which can be exploited by malicious people to compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2008-05-21 |
Secunia Advisory ID: SA30125 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in CMS, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2008-05-14 |
Secunia Advisory ID: SA30230 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Exposure of sensitive information Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in CMS, which can be exploited by malicious, local users to disclose sensitive information or potentially perform actions with escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2008-04-23 |
Secunia Advisory ID: SA29817 |
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]
|
|
|
|
|
|
Release Date: 2008-03-17 |
Secunia Advisory ID: SA29379 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Security Bypass DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious people to bypass certain security restrictions and cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2008-02-19 |
Secunia Advisory ID: SA28997 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Exposure of sensitive information
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS, which can be exploited by malicious, local users to disclose potentially sensitive information. [Read More]
|
|
|
|
|
|
Release Date: 2008-02-14 |
Secunia Advisory ID: SA28941 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: 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) or to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2008-02-04 |
Secunia Advisory ID: SA28740 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in various Avaya products, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2008-01-29 |
Secunia Advisory ID: SA28693 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Exposure of sensitive information Privilege escalation DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS (Call Management System), which can be exploited by malicious, local users to cause a DoS (Denial of Service), disclose potentially sensitive information, or to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2008-01-25 |
Secunia Advisory ID: SA28621 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: Privilege escalation DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS / IR, which can be exploited by malicious, local users to cause a DoS (Denial of Service), or to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2007-12-12 |
Secunia Advisory ID: SA28057 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS / IR, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-11-13 |
Secunia Advisory ID: SA27654 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Exposure of sensitive information
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and IR, which can be exploited by malicious, local users to disclose potentially sensitive information. [Read More]
|
|
|
|
|
|
Release Date: 2007-11-05 |
Secunia Advisory ID: SA27536 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS and IR, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-10-31 |
Secunia Advisory ID: SA27459 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Spoofing
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and IR, which can be exploited by malicious people to poison the DNS cache. [Read More]
|
|
|
|
|
|
Release Date: 2007-10-25 |
Secunia Advisory ID: SA27386 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: DoS
|
Where: From local network |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and IR, which can be exploited by malicious, local users and malicious users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-10-03 |
Secunia Advisory ID: SA27019 |
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: 2007-10-03 |
Secunia Advisory ID: SA27059 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and IR, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-09-07 |
Secunia Advisory ID: SA26731 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a security issue in Avaya CMS and IR, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-08-07 |
Secunia Advisory ID: SA26344 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: Exposure of system information Exposure of sensitive information Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS / IR, which can be exploited by malicious, local users to perform certain actions with escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2007-07-25 |
Secunia Advisory ID: SA26210 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a weakness in Avaya CMS / IR, which can be exploited by malicious, local users to perform certain actions with escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2007-07-20 |
Secunia Advisory ID: SA26125 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a weakness in Avaya CMS and IR, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-07-20 |
Secunia Advisory ID: SA26136 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS / IR, which can be exploited by malicious, local users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2007-07-04 |
Secunia Advisory ID: SA25936 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a weakness in Avaya CMS and IR, which can be exploited by malicious, local users to perform certain actions with escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2007-06-28 |
Secunia Advisory ID: SA25879 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: DoS
|
Where: From local network |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and IR, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-06-14 |
Secunia Advisory ID: SA25661 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS (Call Management System), which can be exploited by malicious users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-05-10 |
Secunia Advisory ID: SA25216 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Exposure of sensitive information Privilege escalation DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS and IR, which can be exploited by malicious, local users to disclose sensitive information, cause a DoS (Denial of Service), and gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2007-05-03 |
Secunia Advisory ID: SA25112 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and IR, which can be exploited by malicious, local users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2007-04-23 |
Secunia Advisory ID: SA24987 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS / IR, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-03-07 |
Secunia Advisory ID: SA24405 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: Manipulation of data Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and IR, which can be exploited by malicious, local users to perform certain actions with escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2007-02-22 |
Secunia Advisory ID: SA24247 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Privilege escalation System access
|
Where: From local network |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya CMS (Call Management System), which can be exploited by malicious, local users to gain escalated privileges or by malicious users to compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2007-02-05 |
Secunia Advisory ID: SA24056 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: DoS
|
Where: From local network |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS / IR, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-01-30 |
Secunia Advisory ID: SA23991 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability and a security issue in Avaya CMS / IR, which can be exploited by malicious, local users to disclose sensitive information or potentially gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2006-12-15 |
Secunia Advisory ID: SA23400 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS System access
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS / IR, which can be exploited by malicious people to cause a DoS (Denial of Service) and potentially compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2006-11-20 |
Secunia Advisory ID: SA22992 |
Solution Status: Vendor Workaround |
|
Criticality:
 |
Impact: Exposure of system information
|
Where: Local system |
|
Short Description: Avaya has acknowledged a security issue in CMS, which can be exploited by malicious, local users to gain access to system information. [Read More]
|
|
|
|
|
|
Release Date: 2006-10-26 |
Secunia Advisory ID: SA22587 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in CMS / IR, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2006-10-26 |
Secunia Advisory ID: SA22581 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in CMS, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2006-10-06 |
Secunia Advisory ID: SA22295 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya Call Management System, which can be exploited by malicious, local users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2006-09-19 |
Secunia Advisory ID: SA21993 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya Call Management System, which can be exploited by malicious, local users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2006-08-30 |
Secunia Advisory ID: SA21647 |
Solution Status: Vendor Workaround |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and IR, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2006-04-18 |
Secunia Advisory ID: SA19716 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and Avaya IR, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2006-04-14 |
Secunia Advisory ID: SA19676 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: System access
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya CMS and Avaya IR, which can be exploited by malicious people to compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2006-03-04 |
Secunia Advisory ID: SA19087 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Security Bypass Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in CMS and IR, which can be exploited by malicious, local users to gain escalated privileges and to bypass certain security restrictions. [Read More]
|
|
|
|
|
|
Release Date: 2005-10-19 |
Secunia Advisory ID: SA17258 |
Solution Status: Vendor Workaround |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in CMS, which potentially can be exploited by malicious, local users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2005-08-23 |
Secunia Advisory ID: SA16546 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: Manipulation of data
|
Where: From local network |
|
Short Description: Avaya has acknowledged a vulnerability in CMS and IR, which can be exploited by malicious users to delete files on a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2005-08-02 |
Secunia Advisory ID: SA16278 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in CMS and IR, which can be exploited by malicious, local users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2005-06-30 |
Secunia Advisory ID: SA15877 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Manipulation of data
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya Call Management System (CMS) and Avaya Interactive Response (IR), which can be exploited by malicious, local users to overwrite arbitrary files on a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date: 2005-06-08 |
Secunia Advisory ID: SA15624 |
Solution Status: Vendor Workaround |
|
Criticality:
 |
Impact: DoS
|
Where: From remote |
|
Short Description: Avaya has acknowledged a vulnerability in Call Management System (CMS), which can be exploited by malicious users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2005-05-16 |
Secunia Advisory ID: SA15384 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Hijacking
|
Where: Local system |
|
Short Description: Avaya has acknowledged some vulnerabilities in Avaya Call Management System (CMS) and Avaya Interactive Response (IR), which can be exploited by malicious, local users to hijack network ports. [Read More]
|
|
|
|
|
|
Release Date: 2005-05-11 |
Secunia Advisory ID: SA15303 |
Solution Status: Vendor Workaround |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya Call Management System (CMS), which can be exploited by malicious, local users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2005-05-10 |
Secunia Advisory ID: SA15313 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in Avaya Call Management System (CMS) and Avaya Interactive Response (IR), which can be exploited by malicious, local users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2005-02-07 |
Secunia Advisory ID: SA14153 |
Solution Status: Unpatched |
|
Criticality:
 |
Impact: DoS
|
Where: Local system |
|
Short Description: Avaya has acknowledged a vulnerability in CMS, which potentially can be exploited by malicious, local users to cause a DoS (Denial of Service). [Read More]
|
|
|