{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-3380 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-3380 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-3380 is a medium-severity vulnerability in n/a, published on 29 Sep 2010. 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-2010-3380 and fix it if it is affected.\n\nWhat it is: CVE-2010-3380 is a medium-severity vulnerability in n/a, published on 29 Sep 2010. 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-2010-3380 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-2010-3380/ (Markdown: https://insights.sbomify.com/CVE-2010-3380/index.md)","id":"CVE-2010-3380","markdown":"https://insights.sbomify.com/CVE-2010-3380/index.md","name":"CVE-2010-3380","record":{"aliases":["GHSA-7v2h-qj3r-6whx"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SLURM workload manager","requires_auth":"low_privilege","summary":"Local attackers can gain privileges by placing a malicious shared library in the current working directory due to insecure LD_LIBRARY_PATH settings in SLURM init scripts.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"slurm","vendor":"llnl"}],"cvss":{"score":6.9,"severity":"medium","source":"nvd","vector":"AV:L/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"The (1) init.d/slurm and (2) init.d/slurmdbd scripts in SLURM before 2.1.14 place the . (dot) directory in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse shared library 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 n/a","id":"CVE-2010-3380","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2010"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2010-3381"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2010-3378"},"products":["n/a"],"published":"2010-09-29","related":[{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2009-2084","kev_date_added":null,"published":"2009-06-16"},{"cvss_score":5,"headline":"Security feature bypass in n/a","id":"CVE-2009-0128","kev_date_added":null,"published":"2009-01-15"}],"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-09-17","vendors":["n/a"]},"summary":"Local attackers can gain privileges by placing a malicious shared library in the current working directory due to insecure LD_LIBRARY_PATH settings in SLURM init scripts.","url":"https://insights.sbomify.com/CVE-2010-3380/"}