Skip to content
Server Security Center
KEVhigh7.5

CVE-2020-36193: PEAR Archive_Tar Improper Link Resolution

PEAR Archive_Tar · listed in the CISA catalog of actively exploited vulnerabilities since 2022-08-25.

CVSS v3.1 (CVE record)
7.5
high
EPSS (exploit probability, 30 days)
71%
higher than 99.4% of all CVEs
Added to CISA KEV
2022-08-25
US federal due date 2022-09-15
Ubuntu priority
medium

CVE-2020-36193 explained

CVE-2020-36193 is a flaw in Tar.php in PEAR Archive_Tar through 1.4.11. Inadequate checking of symbolic links allows write operations with directory traversal, so extracting a crafted archive can write files outside the intended directory. It is related to CVE-2020-28948 and is listed in the CISA Known Exploited Vulnerabilities catalog.

Impact

An attacker who can supply a tar archive to an application using Archive_Tar can cause files to be written outside the target extraction directory. According to the CVSS vector, the attack works over the network with low complexity, no privileges and no user interaction. The impact is on integrity: files can be created or overwritten. Confidentiality and availability are not directly affected. The flaw is known to have been exploited.

Who is affected

On Ubuntu, the php-pear source package is affected. Fixed versions exist in the standard archive. Ubuntu 16.04 LTS is fixed in 1:1.10.1+submodules+notgz-6ubuntu0.3, but that release is end of life. Ubuntu 18.04 LTS is fixed in 1:1.10.5+submodules+notgz-1ubuntu1.18.04.3. Ubuntu 20.04 LTS is fixed in 1:1.10.9+submodules+notgz-1ubuntu0.20.04.2. Standard support has ended for 18.04 and 20.04, and further fixes for them are only available with Ubuntu Pro (ESM).

Written with AI from the data on this page and checked against it automatically.

Official description

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.

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Check the installed php-pear version on each system against the fixed version for its release.
  2. Update php-pear to the fixed version or later from the archive.
  3. Restart PHP services, such as PHP-FPM or web servers, so they load the updated code.
  4. Upgrade Ubuntu 16.04 LTS systems to a supported release, because 16.04 is end of life.
  5. On 18.04 and 20.04, enable Ubuntu Pro (ESM) to keep receiving security fixes, or upgrade to a supported release.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace php-pear with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="php-pear"'

2. Compare each installed version with the fixed version for your release from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="php-pear"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Partial – limited control or information

Weakness: CWE-59 Improper Link Resolution Before File Access ('Link Following')

Questions about CVE-2020-36193

Is this vulnerability being exploited?
Yes. CISA added CVE-2020-36193 to its Known Exploited Vulnerabilities catalog on 2022-08-25. Whether it has been used in ransomware campaigns is listed as unknown. The required action is to apply updates per vendor instructions.
Do I need to restart anything after updating?
Yes. Long-running PHP processes keep using the old code until they are restarted. Restart PHP-FPM, web servers or other services that use Archive_Tar after the update.
Is CVE-2020-36193 the same as CVE-2020-28948?
No. It is a related issue. CVE-2020-36193 concerns inadequate checking of symbolic links that allows write operations with directory traversal in Archive_Tar through 1.4.11.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.