{"answers":{"affected":"3 open source packages ship an affected version, including pyro. It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-2765 in the wild and no public exploit code.","fix":"Upgrade pyro to 3.15 or later.","what":"CVE-2011-2765 is a high-severity path traversal vulnerability in n/a, published on 20 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-2765 and fix it if it is affected.\n\nWhat it is: CVE-2011-2765 is a high-severity path traversal vulnerability in n/a, published on 20 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2011-2765 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pyro (PyPI): affected all versions; fixed in 3.15\n- pyro (PyPI): affected all versions; fixed in 3.15\n- pyro (PyPI): affected all versions; fixed in 3.15\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-2011-2765/ (Markdown: https://insights.sbomify.com/CVE-2011-2765/index.md)","id":"CVE-2011-2765","markdown":"https://insights.sbomify.com/CVE-2011-2765/index.md","name":"CVE-2011-2765","record":{"aliases":["GHSA-xrr4-74mc-rpjc","PYSEC-2018-99"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Python Pyro library","requires_auth":"none","summary":"An attacker can overwrite arbitrary files via symlink attacks on insecurely handled PID files, potentially leading to privilege escalation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pyro","vendor":"pyro_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"pyro before 3.15 unsafely handles pid files in temporary directory locations and opening the pid file as root. An attacker can use this flaw to overwrite arbitrary files via symlinks.","ecosystems":["PyPI"],"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":"Insecure temporary file handling","id":"CVE-2011-2765","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2011"},"n_packages":3,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2011-2766"},"packages":[{"ecosystem":"PyPI","fixed":["3.15"],"introduced":["0"],"last_affected":[],"package":"pyro","purl":null,"source":"GHSA-xrr4-74mc-rpjc"},{"ecosystem":"PyPI","fixed":["3.15"],"introduced":["0"],"last_affected":[],"package":"pyro","purl":"pkg:pypi/pyro","source":"GHSA-xrr4-74mc-rpjc"},{"ecosystem":"PyPI","fixed":["3.15"],"introduced":["0"],"last_affected":[],"package":"pyro","purl":"pkg:pypi/pyro","source":"PYSEC-2018-99"}],"prev":{"headline":"File upload in n/a","id":"CVE-2011-2764"},"products":["n/a"],"published":"2018-08-20","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":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-09-16","vendors":["n/a"]},"summary":"An attacker can overwrite arbitrary files via symlink attacks on insecurely handled PID files, potentially leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2011-2765/"}