CVE-2008-5180 json
Microsoft Communicator, and Communicator in Microsoft Office 2010 beta, allows remote attackers to cause a denial of service (memory consum…
published 2008-11-20 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-5158
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 68.0%
- EPSS 68.0% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 2
- Exploit-DB
Summary
Microsoft Communicator, and Communicator in Microsoft Office 2010 beta, allows remote attackers to cause a denial of service (memory consumption) via a large number of SIP INVITE requests, which trigger the creation of many sessions.
Timeline
- Published
- First public exploit (EDB-7262)
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
67.98% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
exploit-db.com
/exploits/7262
exploit, third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/12079
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/39221
vdb-entry, broken-link, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/46673
vdb-entry, third-party-advisory
-
securitytracker.com
/id?1021294
vdb-entry, broken-link, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/57581
vdb-entry, third-party-advisory
-
voipshield.com
/research-details.php?id=133
broken-link
-
secunia.com
/advisories/32940
third-party-advisory, broken-link
Sources
- CVE List CVE-2008-5180
- NVD CVE-2008-5180
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.