Winvnc vulnerabilitiesRanked by how likely they are to be used.
Winvnc is made by Att. We track 4 published vulnerabilities listed under that exact name, across 2 versions. None of them is on the list of flaws known to be exploited today. Att lists newer releases under their own names, such as Winvnc Server, so check those pages too.
We keep watching the known-exploited list.
Is Winvnc listed under other names? Yes.
Att also lists Winvnc under more specific names, such as Winvnc Server. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Winvnc vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Winvnc's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Winvnc 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.
- 71%CVE-2001-0168Critical
Buffer overflow in AT&T WinVNC (Virtual Network Computing) server 3.3.3r7 and earlier allows remote attackers to execute arbitrary commands via a long HTTP GET request when the DebugLevel registry key is greater than 0.
- 51%CVE-2001-0167High
Buffer overflow in AT&T WinVNC (Virtual Network Computing) client 3.3.3r7 and earlier allows remote attackers to execute arbitrary commands via a long rfbConnFailed packet with a long reason string.
- 2.1%CVE-2001-1422High
WinVNC 3.3.3 and earlier generates the same challenge string for multiple connections, which allows remote attackers to bypass VNC authentication by sniffing the challenge and response of other users.
- 1.5%CVE-2000-1164Critical
WinVNC installs the WinVNC3 registry key with permissions that give Special Access (read and modify) to the Everybody group, which allows users to read and modify sensitive information such as passwords and gain...
Running Winvnc? 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
Buffer overflow in AT&T WinVNC (Virtual Network Computing) server 3.3.3r7 and earlier allows remote attackers to execute arbitrary commands via a long HTTP GET request when the DebugLevel registry key is greater than 0.
- Matched to
- Winvnc 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 4 published vulnerabilities listed under the name Winvnc, across 2 versions.
None of Winvnc's vulnerabilities is on the list of flaws known to be exploited today.
Att also lists Winvnc under more specific names, such as Winvnc Server. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Winvnc. 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.