{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-2095 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-2095 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-2095 is a medium-severity path traversal vulnerability in n/a, published on 5 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-2095 and fix it if it is affected.\n\nWhat it is: CVE-2002-2095 is a medium-severity path traversal vulnerability in n/a, published on 5 Aug 2005. 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-2002-2095 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-2002-2095/ (Markdown: https://insights.sbomify.com/CVE-2002-2095/index.md)","id":"CVE-2002-2095","markdown":"https://insights.sbomify.com/CVE-2002-2095/index.md","name":"CVE-2002-2095","record":{"aliases":["GHSA-497q-g5jr-qr43"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Hellbent webserver","requires_auth":"none","summary":"Attackers can read sensitive files by creating similar filenames in the web root, exposing configuration data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hellbent","vendor":"joe_testa"}],"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":"Joe Testa hellbent 01 webserver allows attackers to read files that are specified in the hellbent.prefs file by creating a file with a similar name in the web root, as demonstrated using (1) index.webroot and (2) index.ipallow.","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":"Path traversal in n/a","id":"CVE-2002-2095","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2002"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2002-2096"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2002-2094"},"products":["n/a"],"published":"2005-08-05","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-09-16","vendors":["n/a"]},"summary":"Attackers can read sensitive files by creating similar filenames in the web root, exposing configuration data.","url":"https://insights.sbomify.com/CVE-2002-2095/"}