{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2013-2012 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-2012 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-2012 is a high-severity vulnerability in Debian Debian Linux, published on 31 Oct 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2013-2012 and fix it if it is affected.\n\nWhat it is: CVE-2013-2012 is a high-severity vulnerability in Debian Debian Linux, published on 31 Oct 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2013-2012 in the wild and no public exploit code.\n\nAffected product: Debian Debian Linux. 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-2013-2012/ (Markdown: https://insights.sbomify.com/CVE-2013-2012/index.md)","id":"CVE-2013-2012","markdown":"https://insights.sbomify.com/CVE-2013-2012/index.md","name":"CVE-2013-2012","record":{"aliases":["GHSA-fxr5-v78q-9qq4"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"autojump utility","requires_auth":"low_privilege","summary":"Local attackers can gain privileges by placing a Trojan horse directory in the current working directory during autojump installation.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"autojump","vendor":"autojump_project"},{"product":"debian_linux","vendor":"debian"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"autojump before 21.5.8 allows local users to gain privileges via a Trojan horse custom_install directory in the current working directory.","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":"Privilege escalation in autojump","id":"CVE-2013-2012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux"],"type":"privilege_escalation","year":"2013"},"n_packages":0,"n_references":6,"next":{"headline":"python-keystoneclient unsecure user password update","id":"CVE-2013-2013"},"packages":[],"prev":{"headline":"Code injection in Super Cache Plugin","id":"CVE-2013-2011"},"products":["autojump"],"published":"2019-10-31","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["autojump"]},"summary":"Local attackers can gain privileges by placing a Trojan horse directory in the current working directory during autojump installation.","url":"https://insights.sbomify.com/CVE-2013-2012/"}