{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6890 exists.","fix":"No fix has been published for CVE-2006-6890 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6890 is a high-severity vulnerability in n/a, published on 5 Jan 2007. 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-6890 and fix it if it is affected.\n\nWhat it is: CVE-2006-6890 is a high-severity vulnerability in n/a, published on 5 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6890 exists.\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-6890/ (Markdown: https://insights.sbomify.com/CVE-2006-6890/index.md)","id":"CVE-2006-6890","markdown":"https://insights.sbomify.com/CVE-2006-6890/index.md","name":"CVE-2006-6890","record":{"aliases":["GHSA-4g2q-4rfm-6xj2"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Voodoo chat","requires_auth":"none","summary":"Remote attackers can download user passwords by directly requesting the users.dat file due to insufficient access control.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"voodoo_chat","vendor":"voc-project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Voodoo chat 1.0RC1b stores sensitive information under the web root with insufficient access control, which allows remote attackers to download passwords via a direct request for data/users.dat.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-12-30","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-12-30","kind":"exploitdb","ref":"3044","stars":null,"title":"Voodoo chat 1.0RC1b - 'users.dat' Password Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2006-6890","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2006-6891"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2006-6889"},"products":["n/a"],"published":"2007-01-05","related":[{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2006-3991","kev_date_added":null,"published":"2006-08-05"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can download user passwords by directly requesting the users.dat file due to insufficient access control.","url":"https://insights.sbomify.com/CVE-2006-6890/"}