|
Vulnerability Report: Avaya SIP Enablement Services (SES) 4.x
|
This vulnerability report for Avaya SIP Enablement Services (SES) 4.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 SIP Enablement Services (SES) 4.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
|
11 Secunia advisories
23 Vulnerabilities
|
|
|
Monitor Product
|
Receive alerts for this product
|
|
|
Unpatched
|
100% (11 of 11 Secunia advisories)
|
|
Most Critical Unpatched
The most severe unpatched Secunia advisory affecting Avaya SIP Enablement Services (SES) 4.x, with all vendor patches applied, is rated Moderately critical  .
|
|
|
|
|
|
11 Secunia Advisories in 2003-2009
|
Secunia has issued a total of 11 Secunia advisories in 2003-2009 for Avaya SIP Enablement Services (SES) 4.x. Currently, 100% (11 out of 11) are marked as unpatched with the most severe being rated Moderately critical
More information about the specific Secunia advisories affecting Avaya SIP Enablement Services (SES) 4.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:
2009-11-12 |
Secunia Advisory ID:
SA37298 |
Solution Status:
Unpatched |
|
Criticality:
 |
Impact:
Privilege escalation
DoS
System access
|
Where:
From remote |
|
Short Description:
Avaya has acknowledged some vulnerabilities in multiple Avaya products, which can be exploited by malicious, local users to cause a DoS (Denial of Service) or to potentially gain escalated privileges, and by malicious people to cause a DoS or potentially compromise a user's system. [Read More]
|
|
|
|
|
|
Release Date:
2009-08-14 |
Secunia Advisory ID:
SA36317 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
Security Bypass
Exposure of sensitive information
DoS
|
Where:
From local network |
|
Short Description:
Avaya has acknowledged some security issues and vulnerabilities in multiple Avaya products, which can be exploited by malicious, local users to disclose potentially sensitive information, bypass certain security restrictions, and cause a DoS (Denial of Service), by malicious users to bypass certain security restrictions, and by malicious people to cause a DoS. [Read More]
|
|
|
|
|
|
Release Date:
2009-01-07 |
Secunia Advisory ID:
SA33410 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
System access
|
Where:
From remote |
|
Short Description:
Avaya has acknowledged some vulnerabilities in various Avaya products, which can be exploited by malicious people to compromise a user's system. [Read More]
|
|
|
|
|
|
Release Date:
2009-01-07 |
Secunia Advisory ID:
SA33417 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
DoS
System access
|
Where:
From remote |
|
Short Description:
Avaya has acknowledged some vulnerabilities in various Avaya products, which can be exploited by malicious people to cause a DoS (Denial of Service) or to potentially compromise an application using the Libxml2 library. [Read More]
|
|
|
|
|
|
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-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:
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-09-01 |
Secunia Advisory ID:
SA31685 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
Privilege escalation
DoS
|
Where:
Local system |
|
Short Description:
Avaya has acknowledged some vulnerabilities in various Avaya products, which can be exploited by malicious, local users to cause a DoS (Denial of Service) and potentially gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date:
2008-09-01 |
Secunia Advisory ID:
SA31689 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
DoS
|
Where:
Local system |
|
Short Description:
Avaya has acknowledged a vulnerability in various Avaya products, which can be exploited by malicious, local users to cause a DoS (Denial of Service). [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-06-27 |
Secunia Advisory ID:
SA30751 |
Solution Status:
Unpatched |
|
Criticality:
|
Impact:
Exposure of system information
Exposure of sensitive information
System access
|
Where:
From remote |
|
Short Description:
Some vulnerabilities have been reported in Avaya SIP Enablement Services, which can be exploited by malicious people to disclose sensitive information and by malicious users to compromise a vulnerable system. [Read More]
|
|
|
