Pear vulnerabilitiesRanked by how likely they are to be used.
Pear is made by PHP. We track 5 published vulnerabilities listed under that exact name, across 84 versions. None of them is on the list of flaws known to be exploited today. PHP lists newer releases under their own names, such as Pear Archive Tar, so check those pages too.
We keep watching the known-exploited list.
Is Pear listed under other names? Yes.
PHP also lists Pear under more specific names, such as Pear Archive Tar. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Pear vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Pear's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Pear flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 13%CVE-2017-5630High
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,...
- 7.4%CVE-2005-4154Medium
Unspecified vulnerability in PEAR installer 1.4.2 and earlier allows user-assisted attackers to execute arbitrary code via a crafted package that can execute code when the pear command is executed or when the Web/Gtk...
- 1.8%CVE-2006-0144High
The proxy server feature in go-pear.php in PHP PEAR 0.2.2, as used in Apache2Triad, allows remote attackers to execute arbitrary PHP code by redirecting go-pear.php to a malicious proxy server that provides a...
- 0.5%
The installer in PEAR before 1.9.2 allows local users to overwrite arbitrary files via a symlink attack on the package.xml file, related to the (1) download_dir, (2) cache_dir, (3) tmp_dir, and (4)...
- 0.3%
The installer in PEAR 1.9.2 and earlier allows local users to overwrite arbitrary files via a symlink attack on the package.xml file, related to the (1) download_dir, (2) cache_dir, (3) tmp_dir, and (4)...
Running Pear? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Pear on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 5 published vulnerabilities listed under the name Pear, across 84 versions.
None of Pear's vulnerabilities is on the list of flaws known to be exploited today.
PHP also lists Pear under more specific names, such as Pear Archive Tar. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a EdgeProtect account and track Pear. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.