{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2000-1018 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2000-1018 yet. Limit exposure of the affected software until one is available.","what":"CVE-2000-1018 is a low-severity vulnerability in n/a, published on 22 Jan 2001. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2000-1018 and fix it if it is affected.\n\nWhat it is: CVE-2000-1018 is a low-severity vulnerability in n/a, published on 22 Jan 2001. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2000-1018 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-2000-1018/ (Markdown: https://insights.sbomify.com/CVE-2000-1018/index.md)","id":"CVE-2000-1018","markdown":"https://insights.sbomify.com/CVE-2000-1018/index.md","name":"CVE-2000-1018","record":{"aliases":["GHSA-4jwj-9x7x-p48c"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GNU coreutils shred","requires_auth":"low_privilege","summary":"Local attackers can recover data from files supposedly wiped by the shred utility due to improper buffer flushing and file opening.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"shred","vendor":"mendel_cooper"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"shred 1.0 file wiping utility does not properly open a file for overwriting or flush its buffers, which prevents shred from properly replacing the file's data and allows local users to recover the 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-2000-1018","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2000"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2000-1019"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2000-1017"},"products":["n/a"],"published":"2001-01-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-08","vendors":["n/a"]},"summary":"Local attackers can recover data from files supposedly wiped by the shred utility due to improper buffer flushing and file opening.","url":"https://insights.sbomify.com/CVE-2000-1018/"}