# CVE-2017-5630: PEAR core file overwrite vulnerability

> Remote attackers can overwrite arbitrary files, such as .htaccess, via crafted HTTP responses during PEAR installation, potentially leading to code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5630, GHSA-xxv8-pv43-57x5, UBUNTU-CVE-2017-5630

## What is CVE-2017-5630?

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.

### Official 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.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2017-5630?

2 open source packages ship an affected version, including pear/pear. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pear/pear` | Packagist | All versions to 1.10.1 | None |
| `pear/pear` | Packagist | All versions to 1.10.1 | None |

Products: Php Pear.

## How do I fix CVE-2017-5630?

No fix has been published for CVE-2017-5630 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-5630 being exploited?

There is no known exploitation of CVE-2017-5630 in the wild and no public exploit code.

Public exploit code:

- PHP PEAR 1.10.1 - Arbitrary File Download (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-4154](https://insights.sbomify.com/CVE-2005-4154/): Code injection in n/a (medium 5.1)
- [CVE-2011-1072](https://insights.sbomify.com/CVE-2011-1072/): Path traversal in n/a (low 3.3)
- [CVE-2011-1144](https://insights.sbomify.com/CVE-2011-1144/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5630 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2017-5630 in the wild and no public exploit code.

Affected packages and fixed versions:
- pear/pear (Packagist): affected all versions up to 1.10.1; no fix listed
- pear/pear (Packagist): affected all versions up to 1.10.1; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-5630/ (Markdown: https://insights.sbomify.com/CVE-2017-5630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5630
- OSV: https://osv.dev/vulnerability/CVE-2017-5630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5630/
Summaries are generated and may contain mistakes; the official description above is the record.