ultraseek vulnerabilities and fixes
Recent CVEs affecting ultraseek, with upgrade or downgrade steps. 5 tracked.
ultraseek has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2009-01-29. Highest priority: CVE-2006-5819 (score 58/100).
- CVE-2009-0347 MEDIUM 5.8 DOWNGRADE Open redirect vulnerability in cs.html in the Autonomy (formerly Verity) Ultraseek search engine allows remote
- 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-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
FAQ
How do I fix ultraseek 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 ultraseek being exploited right now?
None of the tracked ultraseek CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which ultraseek 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.