{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-2657 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2005-2657 is a medium-severity vulnerability in n/a, published on 16 Sep 2005. 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-2005-2657 and fix it if it is affected.\n\nWhat it is: CVE-2005-2657 is a medium-severity vulnerability in n/a, published on 16 Sep 2005. 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-2005-2657 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-2005-2657/ (Markdown: https://insights.sbomify.com/CVE-2005-2657/index.md)","id":"CVE-2005-2657","markdown":"https://insights.sbomify.com/CVE-2005-2657/index.md","name":"CVE-2005-2657","record":{"aliases":["DSA-811-2","GHSA-m6q5-3mgq-3978"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Common Lisp Controller","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges by placing malicious code in the cache directory, which is executed by other users.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"debian","cpe":[{"product":"common-lisp-controller","vendor":"common-lisp-controller"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Unknown vulnerability in common-lisp-controller 4.18 and earlier allows local users to gain privileges by compiling arbitrary code in the cache directory, which is executed by another user if the user has not run Common Lisp before.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Privilege escalation in n/a","id":"CVE-2005-2657","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2005"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2005-2658"},"packages":[],"prev":{"headline":"Misconfiguration in n/a","id":"CVE-2005-2656"},"products":["n/a"],"published":"2005-09-16","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-07","vendors":["n/a"]},"summary":"Local attackers can escalate privileges by placing malicious code in the cache directory, which is executed by other users.","url":"https://insights.sbomify.com/CVE-2005-2657/"}