Archive Tar vulnerabilitiesAnd the versions its exploited flaws hit.
Archive Tar is made by PHP. We track 4 published vulnerabilities in it, across 19 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 25 August 2022. If you run Archive Tar, check your version against the exploited flaws below and patch those first.
The most recent Archive Tar flaw added to the known-exploited list is CVE-2020-28949, on 25 August 2022. We keep watching the known-exploited list.
Which versions of Archive Tar do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "before 1.4.12" means every version up to, but not including, 1.4.12. Find your version, then patch.
- CVE-2020-28949Exploited list, 25 Aug 2022
PEAR Archive_Tar Deserialization of Untrusted Data Vulnerability
before 1.4.12 - CVE-2020-36193Exploited list, 25 Aug 2022
PEAR Archive_Tar Improper Link Resolution Vulnerability
up to 1.4.11
Which Archive Tar vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.8PEAR Archive_Tar Deserialization of Untrusted Data Vulnerability
PEAR Archive_Tar allows an unserialization attack because phar: is blocked but PHAR: is not blocked.
- 7.5PEAR Archive_Tar Improper Link Resolution Vulnerability
PEAR Archive_Tar Tar.php allows write operations with directory traversal due to inadequate checking of symbolic links.
Which Archive Tar 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.
- 85%
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.
- 73%CVE-2021-32610High
In Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.
- 71%
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.
- 47%CVE-2020-28948High
Archive_Tar through 1.4.10 allows an unserialization attack because phar: is blocked but PHAR: is not blocked.
Running Archive Tar? 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 flaw being exploited affects software Acme tracks
PEAR Archive_Tar allows an unserialization attack because phar: is blocked but PHAR: is not blocked. PEAR stands for PHP Extension and Application Repository and it is an open-source framework and distribution system for reusable PHP components with known usage in third-party products such as Drupal Core and Red Hat Linux.
- Matched to
- Archive Tar on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 4 published vulnerabilities listed under the name Archive Tar, across 19 versions. The most recent Archive Tar flaw added to the known-exploited list is CVE-2020-28949, on 25 August 2022.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2020-28949 and CVE-2020-36193.
Each flaw names its own versions, usually as ranges. The newest, CVE-2020-28949, affects before 1.4.12. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Archive Tar. 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.