Windows Messenger vulnerabilitiesRanked by how likely they are to be used.
Windows Messenger is made by Microsoft. We track 2 published vulnerabilities in it, across 3 versions. None of them is on the list of flaws known to be exploited today. If you run Windows Messenger, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Windows Messenger vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Windows Messenger's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Windows Messenger 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.
- 82%CVE-2004-0597Critical
Multiple buffer overflows in libpng 1.2.5 and earlier, as used in multiple products, allow remote attackers to execute arbitrary code via malformed PNG images in which (1) the png_handle_tRNS function does not...
- 34%CVE-2008-0082Critical
An ActiveX control (Messenger.UIAutomation.1) in Windows Messenger 4.7 and 5.1 is marked as safe-for-scripting, which allows remote attackers to control the Messenger application, and "change state," obtain contact...
Running Windows Messenger? 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
Multiple buffer overflows in libpng 1.2.5 and earlier, as used in multiple products, allow remote attackers to execute arbitrary code via malformed PNG images in which (1) the png_handle_tRNS function does not properly validate the length of transparency chunk (tRNS) data, or the (2) png_handle_sBIT or (3) png_handle_hIST functions do not perform sufficient bounds checking.
- Matched to
- Windows Messenger 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 2 published vulnerabilities listed under the name Windows Messenger, across 3 versions.
None of Windows Messenger's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Windows Messenger. 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.