{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9642 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9642 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9642 is a critical code injection vulnerability in n/a, published on 5 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-9642 and fix it if it is affected.\n\nWhat it is: CVE-2019-9642 is a critical code injection vulnerability in n/a, published on 5 Jun 2019. 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-2019-9642 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-2019-9642/ (Markdown: https://insights.sbomify.com/CVE-2019-9642/index.md)","id":"CVE-2019-9642","markdown":"https://insights.sbomify.com/CVE-2019-9642/index.md","name":"CVE-2019-9642","record":{"aliases":["GHSA-fwvv-q6jf-62c9","UBUNTU-CVE-2019-9642"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Pydio file sharing","requires_auth":"none","summary":"Unauthenticated attackers can execute arbitrary PHP code by uploading a malicious file and accessing it via the proxy endpoint.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pydio","vendor":"pydio"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An issue was discovered in proxy.php in pydio-core in Pydio through 8.2.2. Through an unauthenticated request, it possible to evaluate malicious PHP code by placing it on the fourth line of a .php file, as demonstrated by a PoC.php created by the guest account, with execution via a proxy.php?hash=../../../../../var/lib/pydio/data/personal/guest/PoC.php request. This is related to plugins/action.share/src/Store/ShareStore.php.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in n/a","id":"CVE-2019-9642","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Neutralization of Input During Web Page Generation in Jupyter Notebook","id":"CVE-2019-9644"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-9641"},"products":["n/a"],"published":"2019-06-05","related":[{"cvss_score":9.8,"headline":"Command injection in Ajaxeplorer","id":"CVE-2013-4267","kev_date_added":null,"published":"2020-02-11"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2018-20718","kev_date_added":null,"published":"2019-01-15"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2015-3431","kev_date_added":null,"published":"2017-09-19"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2019-20452","kev_date_added":null,"published":"2020-03-17"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2019-20453","kev_date_added":null,"published":"2020-03-17"},{"cvss_score":7.7,"headline":"Server-side request forgery in n/a","id":"CVE-2019-15033","kev_date_added":null,"published":"2019-09-19"}],"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-04","vendors":["n/a"]},"summary":"Unauthenticated attackers can execute arbitrary PHP code by uploading a malicious file and accessing it via the proxy endpoint.","url":"https://insights.sbomify.com/CVE-2019-9642/"}