{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-1999-0569 in the wild and no public exploit code.","fix":"No fix has been published for CVE-1999-0569 yet. Limit exposure of the affected software until one is available.","what":"CVE-1999-0569 is a critical vulnerability in n/a, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-1999-0569 and fix it if it is affected.\n\nWhat it is: CVE-1999-0569 is a critical vulnerability in n/a, published on 4 Feb 2000. 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-1999-0569 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-1999-0569/ (Markdown: https://insights.sbomify.com/CVE-1999-0569/index.md)","id":"CVE-1999-0569","markdown":"https://insights.sbomify.com/CVE-1999-0569/index.md","name":"CVE-1999-0569","record":{"aliases":["GHSA-fh4q-wg9v-c46f"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Web server","requires_auth":"none","summary":"Attackers can list directory contents when index files are missing, exposing sensitive file names and structure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"A URL for a WWW directory allows auto-indexing, which provides a list of all files in that directory if it does not contain an index.html file.","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-1999-0569","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"1999"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in n/a","id":"CVE-1999-0570"},"packages":[],"prev":{"headline":"Misconfiguration in n/a","id":"CVE-1999-0568"},"products":["n/a"],"published":"2000-02-04","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-01","vendors":["n/a"]},"summary":"Attackers can list directory contents when index files are missing, exposing sensitive file names and structure.","url":"https://insights.sbomify.com/CVE-1999-0569/"}