CSIRTS // UNIFIED SECURITY ADVISORY FEEDSYS ● ONLINE · POWERED BY INTELFUSIONS.COM

CVE-2020-28949

criticalknown exploitedpublic exploitcovered by 1 sourcefirst seen 2022-08-25
Actively exploited. CVE-2020-28949 is listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-08-25) — exploitation has been observed in the wild, and US federal agencies are required to remediate it under BOD 22-01. Treat patching as urgent.
Public exploit code is available. Proof-of-concept or working exploit code for CVE-2020-28949 is indexed in Metasploit and GitHub PoC. Expect opportunistic scanning and exploitation attempts — prioritize remediation.
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.

CSIRTS triage

What
An unserialization attack is possible due to improper blocking of phar: and PHAR: protocols.
Who is affected
Users of PEAR Archive_Tar in third-party products like Drupal Core and Red Hat Linux.
Urgency
Remediation is urgent as the vulnerability is actively exploited and critical in nature.
Action
Update PEAR Archive_Tar to the latest version to address the deserialization issue.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch CVE-2020-28949

Get an email if CVE-2020-28949 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.

Exploitation outlook

Exploit availability

Public exploit or proof-of-concept code for CVE-2020-28949 is indexed in these free datasets. Available exploit code raises real-world risk independent of the CVSS score.

Advisory coverage (1)

External references

NVD record for CVE-2020-28949

CVE.org record

CISA KEV catalog

Embed the live status

CVE-2020-28949 live status badge — this badge updates automatically when the KEV or exploit status changes. How to embed it →

[![CVE-2020-28949 status](https://www.csirts.com/badge/CVE-2020-28949)](https://www.csirts.com/cve/CVE-2020-28949)