{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1819 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1819 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1819 is a medium-severity path traversal vulnerability in n/a, published on 28 Jun 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-1819 and fix it if it is affected.\n\nWhat it is: CVE-2002-1819 is a medium-severity path traversal vulnerability in n/a, published on 28 Jun 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-1819 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-1819/ (Markdown: https://insights.sbomify.com/CVE-2002-1819/index.md)","id":"CVE-2002-1819","markdown":"https://insights.sbomify.com/CVE-2002-1819/index.md","name":"CVE-2002-1819","record":{"aliases":["GHSA-hgp2-pwm9-wf73"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TinyHTTPD web server","requires_auth":"none","summary":"Remote attackers can read or execute arbitrary files via directory traversal in TinyHTTPD, requiring immediate upgrade.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tinyhttpd","vendor":"tinyhttpd"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:N","version":"2.0"},"cwes":[],"description":"Directory traversal vulnerability in TinyHTTPD 0.1 .0 allows remote attackers to read or execute arbitrary files via a \"..\" (dot dot) in the URL.","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-1819","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":"Auth bypass in n/a","id":"CVE-2002-1820"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2002-1818"},"products":["n/a"],"published":"2005-06-28","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":"Remote attackers can read or execute arbitrary files via directory traversal in TinyHTTPD, requiring immediate upgrade.","url":"https://insights.sbomify.com/CVE-2002-1819/"}