CVE-2006-5970: Medium severity verity ultraseek vulnerability
Verity Ultraseek before 5.7 allows remote attackers to obtain sensitive information via direct requests with (1) a null ("%00") terminated url parameter to help/urlstatusgo.html; or missing parameters to (2) help/header.html, (3) help/footer.html, (4) spell.html, (5) coreforma.html, (6) daterange.html, (7) hits.html, (8) hitsnavbottom.html, (9) indexform.html, (10) indexforma.html, (11) languages.html, (12) nohits.html, (13) onehit1.html, (14) onehit2.html, (15) query.html, (16) queryform0.html, (17) queryform0a.html, (18) queryform1.html, (19) queryform1a.html, (20) queryform2.html, (21) queryform2a.html, (22) quicklinks.html, (23) relatedtopics.html, (24) signin.html, (25) subtopics.html, (26) thesaurus.html, (27) topics.html, (28) hitspagebar.html, (29) highlight/highlight.html, (30) highlight/highlightone.html, and (31) highlight/topnav.html, which leaks the installation path in the resulting error message.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2006-5970?
CVE-2006-5970 is considered a medium severity vulnerability due to the potential exposure of sensitive information.
How do I fix CVE-2006-5970?
To fix CVE-2006-5970, upgrade to Verity Ultraseek version 5.7 or later, which addresses this vulnerability.
What types of attacks are possible with CVE-2006-5970?
CVE-2006-5970 allows remote attackers to exploit the system and obtain sensitive information via specially crafted URL requests.
Which versions of Verity Ultraseek are affected by CVE-2006-5970?
CVE-2006-5970 affects all versions of Verity Ultraseek prior to version 5.7.
Can CVE-2006-5970 impact my organization’s data security?
Yes, CVE-2006-5970 can significantly impact data security by exposing sensitive information to unauthorized users.