Vsu vulnerabilitiesRanked by how likely they are to be used.
Vsu is made by Avaya. We track 3 published vulnerabilities listed under that exact name, across 8 versions. None of them is on the list of flaws known to be exploited today. Avaya lists newer releases under their own names, such as Vsu 100, so check those pages too.
We keep watching the known-exploited list.
Is Vsu listed under other names? Yes.
Avaya also lists Vsu under more specific names, such as Vsu 100 and Vsu 10000. 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 Vsu vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Vsu's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Vsu 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.
- 10%CVE-2004-0112Medium
The SSL/TLS handshaking code in OpenSSL 0.9.7a, 0.9.7b, and 0.9.7c, when using Kerberos ciphersuites, does not properly check the length of Kerberos tickets during a handshake, which allows remote attackers to cause...
- 9.5%CVE-2004-0079High
The do_change_cipher_spec function in OpenSSL 0.9.6c to 0.9.6k, and 0.9.7a to 0.9.7c, allows remote attackers to cause a denial of service (crash) via a crafted SSL/TLS handshake that triggers a null dereference.
- 7.2%CVE-2004-0081Medium
OpenSSL 0.9.6 before 0.9.6d does not properly handle unknown message types, which allows remote attackers to cause a denial of service (infinite loop), as demonstrated using the Codenomicon TLS Test Tool.
Running Vsu? 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
The SSL/TLS handshaking code in OpenSSL 0.9.7a, 0.9.7b, and 0.9.7c, when using Kerberos ciphersuites, does not properly check the length of Kerberos tickets during a handshake, which allows remote attackers to cause a denial of service (crash) via a crafted SSL/TLS handshake that causes an out-of-bounds read.
- Matched to
- Vsu 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 3 published vulnerabilities listed under the name Vsu, across 8 versions.
None of Vsu's vulnerabilities is on the list of flaws known to be exploited today.
Avaya also lists Vsu under more specific names, such as Vsu 100 and Vsu 10000. 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 Vsu. 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.