{"answers":{"affected":"3 open source packages ship an affected version, including pleaser. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-31154 in the wild and no public exploit code.","fix":"Upgrade pleaser to 0.4.0 or later.","what":"CVE-2021-31154 is a high-severity path traversal vulnerability in n/a, published on 27 May 2021. 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-2021-31154 and fix it if it is affected.\n\nWhat it is: CVE-2021-31154 is a high-severity path traversal vulnerability in n/a, published on 27 May 2021. 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-2021-31154 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pleaser (crates.io): affected all versions; fixed in 0.4.0\n- pleaser (crates.io): affected all versions; fixed in 0.4.0\n- pleaser (crates.io): affected from 0.0.0-0; fixed in 0.4.0\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-2021-31154/ (Markdown: https://insights.sbomify.com/CVE-2021-31154/index.md)","id":"CVE-2021-31154","markdown":"https://insights.sbomify.com/CVE-2021-31154/index.md","name":"CVE-2021-31154","record":{"aliases":["DEBIAN-CVE-2021-31154","GHSA-pp74-39w2-v4w9","RUSTSEC-2021-0102"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust pleaseedit library","requires_auth":"low_privilege","summary":"A local attacker can gain root privileges by exploiting predictable temporary filenames in the pleaseedit library via a symlink attack.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pleaseedit","vendor":"pleaseedit_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"pleaseedit in please before 0.4 uses predictable temporary filenames in /tmp and the target directory. This allows a local attacker to gain full root privileges by staging a symlink attack.","ecosystems":["crates.io"],"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":"Permissions bypass in pleaser","id":"CVE-2021-31154","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2021"},"n_packages":3,"n_references":2,"next":{"headline":"Permissions bypass in pleaser","id":"CVE-2021-31155"},"packages":[{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"pleaser","purl":null,"source":"GHSA-pp74-39w2-v4w9"},{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"pleaser","purl":"pkg:cargo/pleaser","source":"GHSA-pp74-39w2-v4w9"},{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"pleaser","purl":"pkg:cargo/pleaser","source":"RUSTSEC-2021-0102"}],"prev":{"headline":"File exposure in pleaser","id":"CVE-2021-31153"},"products":["n/a"],"published":"2021-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"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-03","vendors":["n/a"]},"summary":"A local attacker can gain root privileges by exploiting predictable temporary filenames in the pleaseedit library via a symlink attack.","url":"https://insights.sbomify.com/CVE-2021-31154/"}