CVE-2008-6573 json
Multiple SQL injection vulnerabilities in Avaya SIP Enablement Services (SES) in Avaya Avaya Communication Manager 3.x, 4.0, and 5.0 (1) al…
published 2009-04-01 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-6536
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
Multiple SQL injection vulnerabilities in Avaya SIP Enablement Services (SES) in Avaya Avaya Communication Manager 3.x, 4.0, and 5.0 (1) allow remote attackers to execute arbitrary SQL commands via unspecified vectors related to profiles in the SIP Personal Information Manager (SPIM) in the web interface; and allow remote authenticated users to execute arbitrary SQL commands via unspecified vectors related to (2) permissions for SPIM profiles in the web interface and (3) a crafted SIP request to the SIP server.
Exploit prediction
1.50% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
support.avaya.com
/elmodocs2/security/ASA-2008-151.htm
vendor-advisory
-
secunia.com
/advisories/29744
third-party-advisory, vendor-advisory
- voipshield.com /research-details.php?id=25
- voipshield.com /research-details.php?id=26
- voipshield.com /research-details.php?id=22
-
osvdb.org
/44286
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41733
vdb-entry
-
securityfocus.com
/bid/28682
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41730
vdb-entry
-
osvdb.org
/44284
vdb-entry
-
osvdb.org
/44285
vdb-entry
- support.avaya.com /elmodocs2/security/ASA-2008-150.htm
Sources
- CVE List CVE-2008-6573
- NVD CVE-2008-6573
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.