{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-5970 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-5970 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-5970 is a medium-severity vulnerability in n/a, published on 18 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-5970 and fix it if it is affected.\n\nWhat it is: CVE-2006-5970 is a medium-severity vulnerability in n/a, published on 18 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-5970 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2006-5970/ (Markdown: https://insights.sbomify.com/CVE-2006-5970/index.md)","id":"CVE-2006-5970","markdown":"https://insights.sbomify.com/CVE-2006-5970/index.md","name":"CVE-2006-5970","record":{"aliases":["GHSA-83rm-x85j-52pc"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Verity Ultraseek","requires_auth":"none","summary":"Remote attackers can obtain sensitive installation path information by sending crafted requests to specific HTML files in Verity Ultraseek.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ultraseek","vendor":"verity"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"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/highlight_one.html, and (31) highlight/topnav.html, which leaks the installation path in the resulting error message.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2006-5970","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":8,"next":{"headline":"Path traversal in n/a","id":"CVE-2006-5971"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2006-5969"},"products":["n/a"],"published":"2006-11-18","related":[{"cvss_score":10,"headline":"Server-side request forgery in n/a","id":"CVE-2006-5819","kev_date_added":null,"published":"2006-11-18"},{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2006-5971","kev_date_added":null,"published":"2006-11-18"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2004-0050","kev_date_added":null,"published":"2004-05-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive installation path information by sending crafted requests to specific HTML files in Verity Ultraseek.","url":"https://insights.sbomify.com/CVE-2006-5970/"}