{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-6052 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-6052 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6052 is a medium-severity vulnerability in n/a, published on 22 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-6052 and fix it if it is affected.\n\nWhat it is: CVE-2006-6052 is a medium-severity vulnerability in n/a, published on 22 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-6052 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-6052/ (Markdown: https://insights.sbomify.com/CVE-2006-6052/index.md)","id":"CVE-2006-6052","markdown":"https://insights.sbomify.com/CVE-2006-6052/index.md","name":"CVE-2006-6052","record":{"aliases":["GHSA-2r7v-857w-j9f5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Case Management System","requires_auth":"none","summary":"Remote attackers can enumerate valid usernames in NetEpi Case Manager due to inconsistent error messages, facilitating targeted attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"netepi_case_manager","vendor":"netepi_case_manager"}],"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":"NetEpi Case Manager before 0.98 generates different error messages depending on whether or not a username is valid, which allows remote attackers to enumerate valid usernames.","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-6052","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2006-6053"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2006-6051"},"products":["n/a"],"published":"2006-11-22","related":[],"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 enumerate valid usernames in NetEpi Case Manager due to inconsistent error messages, facilitating targeted attacks.","url":"https://insights.sbomify.com/CVE-2006-6052/"}