CVE-2008-6706 json
Multiple unspecified vulnerabilities in the Web management interface in Avaya SIP Enablement Services (SES) 3.x and 4.0, as used with Avaya…
published 2009-04-10 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-6666
- cvss
- 7.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Multiple unspecified vulnerabilities in the Web management interface in Avaya SIP Enablement Services (SES) 3.x and 4.0, as used with Avaya Communication Manager 3.1.x, allow remote attackers to obtain (1) application server configuration, (2) database server configuration including encrypted passwords, (3) a system utility that decrypts "subscriber table passwords," (4) a system utility that decrypts database passwords, and (5) a system utility that encrypts "subscriber table passwords."
Exploit prediction
2.26% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:C/I:N/A:N |
References
-
support.avaya.com
/elmodocs2/security/ASA-2008-268.htm
vendor-advisory
-
vupen.com
/english/advisories/2008/1943/references
vdb-entry
-
secunia.com
/advisories/30751
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43382
vdb-entry
- voipshield.com /research-details.php?id=81
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43388
vdb-entry
- voipshield.com /research-details.php?id=83
- voipshield.com /research-details.php?id=82
-
osvdb.org
/46602
vdb-entry
- voipshield.com /research-details.php?id=85
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43387
vdb-entry
- voipshield.com /research-details.php?id=84
-
securityfocus.com
/bid/29939
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43383
vdb-entry
Sources
- CVE List CVE-2008-6706
- NVD CVE-2008-6706
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.