CVE-2020-28948

What it is

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

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

47.5% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2020-11-19 00:00 UTC ReservedThe CVE id was reserved by its CNA
2. 2020-11-19 19:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 03:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 47.5% in the next 30 days (EPSS).
• Severity: 7.8 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2020-11-19 19:15 UTC

Last modified

2026-06-17 03:10 UTC

Exploit probability

47.5% · EPSS, next 30 days

Weakness

CWE-502 · Unsafe deserialization

Record status

Modified

Affected

• PHP Archive Tar < 1.4.11
• Debian Linux 9.0
• Debian Linux 10.0
• Fedoraproject Fedora 32
• Fedoraproject Fedora 33
• Fedoraproject Fedora 34
• Fedoraproject Fedora 35
• Drupal < 7.75

Attack profile CVSS 3.1 · 7.8

Attack vector

Local

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-28948.md and follow it. Check whether this project is affected by CVE-2020-28948. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge