{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-1146 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-1146 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1146 is a low-severity path traversal vulnerability in n/a, published on 25 Jun 2002. 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-2001-1146 and fix it if it is affected.\n\nWhat it is: CVE-2001-1146 is a low-severity path traversal vulnerability in n/a, published on 25 Jun 2002. 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-2001-1146 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-1146/ (Markdown: https://insights.sbomify.com/CVE-2001-1146/index.md)","id":"CVE-2001-1146","markdown":"https://insights.sbomify.com/CVE-2001-1146/index.md","name":"CVE-2001-1146","record":{"aliases":["GHSA-9qq9-pcmw-q95w"],"analysis":{"component_type":"operating_system","fix_type":"configuration_change","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"EnGarde Secure Linux","requires_auth":"low_privilege","summary":"Local attackers can modify files via symlink attacks when AllCommerce debugging is enabled in EnGarde Secure Linux.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"allcommerce","vendor":"lee_herron"}],"cvss":{"score":1.2,"severity":"low","source":"nvd","vector":"AV:L/AC:H/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"AllCommerce with debugging enabled in EnGarde Secure Linux 1.0.1 creates temporary files with predictable names, which allows local users to modify files via a symlink attack.","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-2001-1146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2001"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2001-1147"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2001-1145"},"products":["n/a"],"published":"2002-06-25","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 modify files via symlink attacks when AllCommerce debugging is enabled in EnGarde Secure Linux.","url":"https://insights.sbomify.com/CVE-2001-1146/"}