|
Vulnerability Report: Avaya Modular Messaging 2.x
|
This vulnerability report for Avaya Modular Messaging 2.x 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 Modular Messaging 2.x 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
|
103 Secunia advisories
255 Vulnerabilities
|
|
|
Monitor Product
|
Receive alerts for this product
|
|
|
Unpatched
|
73% (75 of 103 Secunia advisories)
|
|
Most Critical Unpatched
The most severe unpatched Secunia advisory affecting Avaya Modular Messaging 2.x, with all vendor patches applied, is rated Highly critical  .
|
|
|
|
|
|
13 Secunia Advisories in 2008
|
Secunia has issued a total of 13 Secunia advisories in 2008 for Avaya Modular Messaging 2.x. Currently, 100% (13 out of 13) are marked as unpatched with the most severe being rated Moderately critical 
More information about the specific Secunia advisories affecting Avaya Modular Messaging 2.x 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:
2008-12-10 |
Secunia Advisory ID:
SA33095 |
Solution Status:
Unpatched |
|
Criticality:
 |
Impact:
DoS
|
Where:
From local network |
|
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-12-10 |
Secunia Advisory ID:
SA33085 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
System access
|
Where:
From local network |
|
Short Description:
Avaya has acknowledged some vulnerabilities in Messaging Storage Server, which potentially can be exploited by malicious people to compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date:
2008-12-05 |
Secunia Advisory ID:
SA33005 |
Solution Status:
Unpatched |
|
Criticality:
 |
Impact:
System access
|
Where:
From remote |
|
Short Description:
Avaya has acknowledged a security issue in various Avaya products, which can be exploited by malicious people to compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date:
2008-10-17 |
Secunia Advisory ID:
SA32294 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
DoS
|
Where:
From remote |
|
Short Description:
Avaya has acknowledged some vulnerabilities in various Avaya products, which can be exploited by malicious users and malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date:
2008-10-17 |
Secunia Advisory ID:
SA32306 |
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-10-17 |
Secunia Advisory ID:
SA32313 |
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-10-14 |
Secunia Advisory ID:
SA32265 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
DoS
System access
|
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) or potentially compromise an application using the library. [Read More]
|
|
|
|
|
|
Release Date:
2008-10-14 |
Secunia Advisory ID:
SA32241 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
Unknown
|
Where:
From remote |
|
Short Description:
Avaya has acknowledged that a small number of OpenSSH packages have been tampered with. [Read More]
|
|
|
|
|
|
Release Date:
2008-08-25 |
Secunia Advisory ID:
SA31604 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
DoS
System access
|
Where:
From remote |
|
Short Description:
Avaya has acknowledged a vulnerability in various Avaya products, which can potentially be exploited by malicious people to compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date:
2008-08-22 |
Secunia Advisory ID:
SA31568 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
Spoofing
DoS
System access
|
Where:
From local network |
|
Short Description:
Avaya has acknowledged some vulnerabilities in various Avaya products, which can be exploited by malicious people to spoof authenticated SNMPv3 packets or to potentially compromise a vulnerable system. [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-14 |
Secunia Advisory ID:
SA28469 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
Privilege escalation
|
Where:
Local system |
|
Short Description:
Avaya has acknowledged a vulnerability in multiple Avaya Products, which can be exploited by malicious, local users to perform certain actions with escalated privileges. [Read More]
|
|
|
|
|
|
Release Date:
2008-01-09 |
Secunia Advisory ID:
SA28387 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
DoS
System access
|
Where:
From remote |
|
Short Description:
Avaya has acknowledged a vulnerability in various Avaya products, which potentially can be exploited by malicious people to compromise a vulnerable system. [Read More]
|
|
|
