verity vulnerabilities
Recent CVEs affecting verity products. 7 tracked.
verity has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 5. Most recent: 2006-11-18. Highest priority: CVE-2006-5819 (score 58/100).
- CVE-2006-5971 MEDIUM 5.0 UPGRADE Absolute path traversal vulnerability in admin/logfile.txt in Verity Ultraseek before 5.6.2 allows remote atta
- CVE-2006-5970 MEDIUM 5.0 UPGRADE Verity Ultraseek before 5.7 allows remote attackers to obtain sensitive information via direct requests with (
- CVE-2006-5819 HIGH 10.0 UPGRADE Verity Ultraseek before 5.7 allows remote attackers to use the server as a proxy for web attacks and host scan
- CVE-2005-0514 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in Verity Ultraseek before 5.3.3 allows remote attackers to inject ar
- CVE-2004-0050 MEDIUM 5.0 UPGRADE Verity Ultraseek before 5.2.2 allows remote attackers to obtain the full pathname of the document root via an
- CVE-2002-1651 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in Verity Search97 allows remote attackers to insert arbitrary web co
- CVE-2002-0370 HIGH 7.5 DOWNGRADE UPGRADE Buffer overflow in the ZIP capability for multiple products allows remote attackers to cause a denial of servi
FAQ
How do I fix verity vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is verity being exploited right now?
None of the tracked verity CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which verity CVE should I patch first?
CVE-2006-5819 currently ranks highest (58/100): Verity Ultraseek before 5.7 allows remote attackers to use the server as a proxy for web attacks and host scan.