Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

CVE-2020-28948

HIGH

CVE-2020-28948 is a high-severity (CVSS 7.8) Deserialization of Untrusted Data vulnerability in pear/archive_tar. 5 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2020-28948 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Multiple vulnerabilities through filename manipulation in Archive_Tar

Also known asBIT-drupal-2020-28948BIT-drupal-2020-28949CVE-2020-28949DRUPAL-CORE-2020-013GHSA-75c5-f4gw-38r9GHSA-jh5x-hfhg-78jq
Published
Nov 19, 2020
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
5 known

Blast Radius

1 pkg affected
🐘pear/archive_tar

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Archive_Tar through 1.4.10 allows an unserialization attack because phar: is blocked but PHAR: is not blocked.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistpear/archive_tarall versions1.4.11
Exploits & PoCs
5

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pear/archive_tar. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update pear/archive_tar to 1.4.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28948 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2020-28948 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2020-28948. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Archive_Tar through 1.4.10 allows an unserialization attack because phar: is blocked but PHAR: is not blocked.
O3 Security · Impact-Aware SCA

Is CVE-2020-28948 in your dependencies?

O3 detects CVE-2020-28948 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.