Skip to content
Fencer Intel
high 7.5

CVE-2017-5630 in the critical feed json

PEAR core file overwrite vulnerability

published 2017-02-01 9 y ago modified 2026-06-17 4 mo ago also GHSA-xxv8-pv43-57x5 , EUVD-2022-5878

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.5%
EPSS 12.5% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-5630 updated cvss 3.4

php-pear: File overwrite by malicious server

  • Red Hat Enterprise Linux 5 php-pear Red Hat Enterprise Linux 6 php-pear Red Hat Enterprise Linux 7 php-pear Red Hat Software Collections rh-php56-php-pear, rh-php70-php-pear
    affected: workaround, no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-41185)
  2. Published

Exploit prediction

12.51% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-41185 PHP PEAR 1.10.1 - Arbitrary File Download webapps, 2017-01-30

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
packagist pear/pear
<=1.10.1
no fix listed

Classification

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

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.