{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-0073 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-0073 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-0073 is a low-severity memory corruption vulnerability in n/a, published on 2 Feb 2001."},"fix_prompt":"Check this codebase for CVE-2001-0073 and fix it if it is affected.\n\nWhat it is: CVE-2001-0073 is a low-severity memory corruption vulnerability in n/a, published on 2 Feb 2001. \nExploitation: There is no known exploitation of CVE-2001-0073 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-2001-0073/ (Markdown: https://insights.sbomify.com/CVE-2001-0073/index.md)","id":"CVE-2001-0073","markdown":"https://insights.sbomify.com/CVE-2001-0073/index.md","name":"CVE-2001-0073","record":{"aliases":["GHSA-hv5v-h4qh-vgxj"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_modify"],"network_reachable":"unknown","non_default_config":false,"product_category":"SELinux library","requires_auth":"unknown","summary":"A buffer overflow in the SELinux library allows attackers to modify critical memory data, potentially compromising system integrity.","user_interaction":"unknown","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"security-enhanced_linux","vendor":"nsa"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"Buffer overflow in the find_default_type function in libsecure in NSA Security-enhanced Linux, which may allow attackers to modify critical data in memory.","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":"Memory corruption in n/a","id":"CVE-2001-0073","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2001"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2001-0074"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2001-0072"},"products":["n/a"],"published":"2001-02-02","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":"A buffer overflow in the SELinux library allows attackers to modify critical memory data, potentially compromising system integrity.","url":"https://insights.sbomify.com/CVE-2001-0073/"}