{"answers":{"affected":"2 open source packages ship an affected version, including pear/pear. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5630 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5630 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5630 is a high-severity path traversal vulnerability in n/a, published on 1 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-5630 and fix it if it is affected.\n\nWhat it is: CVE-2017-5630 is a high-severity path traversal vulnerability in n/a, published on 1 Feb 2017. 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-2017-5630 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pear/pear (Packagist): affected all versions up to 1.10.1; no fix listed\n- pear/pear (Packagist): affected all versions up to 1.10.1; no fix listed\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-2017-5630/ (Markdown: https://insights.sbomify.com/CVE-2017-5630/index.md)","id":"CVE-2017-5630","markdown":"https://insights.sbomify.com/CVE-2017-5630/index.md","name":"CVE-2017-5630","record":{"aliases":["DEBIAN-CVE-2017-5630","GHSA-xxv8-pv43-57x5","UBUNTU-CVE-2017-5630"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PEAR Base System","requires_auth":"none","summary":"Remote attackers can overwrite arbitrary files, such as .htaccess, via crafted HTTP responses during PEAR installation, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pear","vendor":"php"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"PECL in the download utility class in the Installer in PEAR Base System v1.10.1 does not validate file types and filenames after a redirect, which allows remote HTTP servers to overwrite files via crafted responses, as demonstrated by a .htaccess overwrite.","ecosystems":["Packagist"],"exploits":{"exploitdb":1,"first_seen":"2017-01-30","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-01-30","kind":"exploitdb","ref":"41185","stars":null,"title":"PHP PEAR 1.10.1 - Arbitrary File Download"}],"tier":"poc_unverified"},"has_fix":false,"headline":"PEAR core file overwrite vulnerability","id":"CVE-2017-5630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2017"},"n_packages":2,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-5631"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["1.10.1"],"package":"pear/pear","purl":null,"source":"GHSA-xxv8-pv43-57x5"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["1.10.1"],"package":"pear/pear","purl":"pkg:composer/pear/pear","source":"GHSA-xxv8-pv43-57x5"}],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2017-5628"},"products":["n/a"],"published":"2017-02-01","related":[{"cvss_score":5.1,"headline":"Code injection in n/a","id":"CVE-2005-4154","kev_date_added":null,"published":"2005-12-11"},{"cvss_score":3.3,"headline":"Path traversal in n/a","id":"CVE-2011-1072","kev_date_added":null,"published":"2011-03-03"},{"cvss_score":3.3,"headline":"Path traversal in n/a","id":"CVE-2011-1144","kev_date_added":null,"published":"2011-03-03"}],"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":"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-05","vendors":["n/a"]},"summary":"Remote attackers can overwrite arbitrary files, such as .htaccess, via crafted HTTP responses during PEAR installation, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2017-5630/"}