{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-4018 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2009-4018 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-4018 is a high-severity vulnerability in Php Php, published on 27 Nov 2009. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-4018 and fix it if it is affected.\n\nWhat it is: CVE-2009-4018 is a high-severity vulnerability in Php Php, published on 27 Nov 2009. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2009-4018 in the wild and no public exploit code.\n\nAffected product: Php Php. 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-2009-4018/ (Markdown: https://insights.sbomify.com/CVE-2009-4018/index.md)","id":"CVE-2009-4018","markdown":"https://insights.sbomify.com/CVE-2009-4018/index.md","name":"CVE-2009-4018","record":{"aliases":["GHSA-64wx-q8pj-gj2r"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"PHP scripting language","requires_auth":"low_privilege","summary":"Attackers can bypass PHP safe mode restrictions to execute arbitrary code with modified environment variables, requiring safe mode to be enabled.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"php","vendor":"php"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"The proc_open function in ext/standard/proc_open.c in PHP before 5.2.11 and 5.3.x before 5.3.1 does not enforce the (1) safe_mode_allowed_env_vars and (2) safe_mode_protected_env_vars directives, which allows context-dependent attackers to execute programs with an arbitrary environment via the env parameter, as demonstrated by a crafted value of the LD_LIBRARY_PATH environment variable.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2010-03-05","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2010-03-05","kind":"exploitdb","ref":"11636","stars":null,"title":"Kolang 4.3.10 \u003c 5.3.0 - 'proc_open()' PHP 'safe_mode' Bypass"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2009-4018","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"php:php","products":["php:php"],"type":"security_feature_bypass","year":"2009"},"n_packages":0,"n_references":18,"next":{"headline":"Denial of service in n/a","id":"CVE-2009-4019"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2009-4017"},"products":["n/a"],"published":"2009-11-27","related":[{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2012-2688","kev_date_added":null,"published":"2012-07-20"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-2376","kev_date_added":null,"published":"2012-05-21"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2011-3268","kev_date_added":null,"published":"2011-08-25"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-4143","kev_date_added":null,"published":"2009-12-21"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-5557","kev_date_added":null,"published":"2008-12-23"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-2050","kev_date_added":null,"published":"2008-05-05"},{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2008-2051","kev_date_added":null,"published":"2008-05-05"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Attackers can bypass PHP safe mode restrictions to execute arbitrary code with modified environment variables, requiring safe mode to be enabled.","url":"https://insights.sbomify.com/CVE-2009-4018/"}