HighGHSA-p8q8-jfcv-g2h2CVE-2021-32610DRUPAL-CORE-2021-004

Directory Traversal in Archive_Tar

Published 9 Aug 2021 · Updated 10 Dec 2025

Is your project on an affected pear/archive_tar?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.4.14
Fixed in
1.4.14
Update to the fixed version for your release line, for example:composer require pear/archive_tar:^1.4.14

Details

In Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.

Is GHSA-p8q8-jfcv-g2h2 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected pear/archive_tar, and gives you the command that fixes it.

More advisories for pear/archive_tar

  • HighCVE-2018-1000888Archive_Tar contains Potential RCE if filename starts with phar:// · 7 Jul 2023
  • CriticalCVE-2006-0931PEAR::Archive_Tar Directory Traversal vulnerability · 1 May 2022
  • HighCVE-2020-28948Multiple vulnerabilities through filename manipulation in Archive_Tar · 22 Apr 2021
  • HighCVE-2020-28948Deserialization of Untrusted Data in Archive_Tar · 22 Apr 2021
  • HighCVE-2020-36193Directory Traversal in Archive_Tar · 22 Apr 2021
pear/archive_tar security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.