Office Communicator vulnerabilitiesRanked by how likely they are to be used.
Office Communicator is made by Microsoft. We track 7 published vulnerabilities in it, across 2 versions. None of them is on the list of flaws known to be exploited today. If you run Office Communicator, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Office Communicator vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Office Communicator's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Office Communicator flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 68%CVE-2008-5180Medium
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...
- 22%CVE-2013-1302Critical
Microsoft Communicator 2007 R2, Lync 2010, Lync 2010 Attendee, and Lync Server 2013 do not properly handle objects in memory, which allows remote attackers to execute arbitrary code via an invitation that triggers...
- 17%CVE-2008-3068High
Microsoft Crypto API 5.131.2600.2180 through 6.0, as used in Outlook, Windows Live Mail, and Office 2007, performs Certificate Revocation List (CRL) checks by using an arbitrary URL from a certificate embedded in a...
- 16%CVE-2008-5179Medium
Unspecified vulnerability in Microsoft Office Communications Server (OCS), Office Communicator, and Windows Live Messenger allows remote attackers to cause a denial of service (crash) via a crafted Real-time...
- 13%CVE-2008-5181Medium
Microsoft Communicator allows remote attackers to cause a denial of service (application or device outage) via instant messages containing large numbers of emoticons.
Running Office Communicator? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Office Communicator on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 7 published vulnerabilities listed under the name Office Communicator, across 2 versions.
None of Office Communicator's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Office Communicator. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.