In Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.
Product
ubuntu/php-pear vulnerabilities
7 published CVES affecting ubuntu/php-pear, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 7
- Critical
- 0
- High
- 6
- Medium
- 0
- Low
- 1
- Unscored
- 0
- CISA KEV
- 2
Latest ubuntu/php-pear CVEs
Newest publication first
-
HighCVSS 7.1 EPSS 73.4%
-
HighCVSS 7.5 EPSS 70.6% CISA KEV added 2022-08-25 Exploited in the wild PoC
Tar.php in Archive_Tar through 1.4.11 allows write operations with Directory Traversal due to inadequate checking of symbolic links, a related issue to CVE-2020-28948.
-
HighCVSS 7.8 EPSS 47.5% PoC
Archive_Tar through 1.4.10 allows an unserialization attack because phar: is blocked but PHAR: is not blocked.
-
HighCVSS 7.8 EPSS 84.6% CISA KEV added 2022-08-25 Exploited in the wild Framework module Public exploit PoC
Archive_Tar through 1.4.10 has :// filename sanitization only to address phar attacks, and thus any other stream-wrapper attack (such as file:// to overwrite files) can still succeed.
-
HighCVSS 8.8 EPSS 19.1% Public exploit PoC
PEAR Archive_Tar version 1.4.3 and earlier contains a CWE-502, CWE-915 vulnerability in the Archive_Tar class. There are several file operations with $v_header['filename'] as parameter (such as file_exists, is_file, is_dir, etc). When extract is called without a specific prefix p...
-
HighCVSS 7.5 EPSS 12.5% Public exploit
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.
-
LowCVSS 3.6 EPSS 0.64%
The PEAR_REST class in REST.php in PEAR in PHP through 5.6.0 allows local users to write to arbitrary files via a symlink attack on a (1) rest.cachefile or (2) rest.cacheid file in /tmp/pear/cache/, related to the retrieveCacheFirst and useLocalCache functions.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.