CVE-2020-7063 | Files added to tar with Phar::buildFromIterator have all-access permissions

Exp

In PHP versions 7.2.x below 7.2.28, 7.3.x below 7.3.15 and 7.4.x below 7.4.3, when creating PHAR archive using PharData::buildFromIterator() function, the files are added with default permissions (0666, or all access) even if the original files on the filesystem were with more restrictive permissions. This may result in files having more lax permissions than intended when such archive is extracted.

Published: 2020-02-27 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-7063 is rated High Exploit Risk (63.7/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.60%). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +1.30% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-7063

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-7063

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.30% 1.60% +1.30%
2 2026-03-04 0.24% 0.30% +0.06%
3 2026-03-01 — 0.24% —

Full EPSS history (36 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-7063

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2020-7063

OS Trackers for CVE-2020-7063

vendor priority summary link
alpine medium CVE-2020-7063: 1 source package rows (php7); 1 state rows across 1 repos (edge-community); fixed 1, open 0. https://security.alpinelinux.org/vuln/CVE-2020-7063
debian not yet assigned CVE-2020-7063 not yet assigned priority: Debian including 1 source packages (php7.4), 1 status rows across 1 suites (bullseye): resolved 1. https://security-tracker.debian.org/tracker/CVE-2020-7063
gentoo high CVE-2020-7063: 1 GLSA(s) (202003-57), 1 atom(s) (dev-lang/php); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-7063
redhat medium — https://access.redhat.com/security/cve/CVE-2020-7063
suse medium CVE-2020-7063 severity moderate: SUSE including 893 source package names (apache2-mod_php5, apache2-mod_php5-5.5.14-109.71.1, …), 1913 product×package rows across 54 product lines (SLES for SAP Applications 11 SP2, SUSE CaaS Platform 4.0, … (54 product lines)): Fixed 1253, Known Not Affected 660. https://www.suse.com/security/cve/CVE-2020-7063/
ubuntu low CVE-2020-7063 low priority: Ubuntu including 5 source packages (php5, php7.0, php7.2, php7.3, php7.4), 25 status rows across 5 suites (bionic, eoan, trusty, upstream, xenial): DNE 16, released 6, needs-triage 3. https://ubuntu.com/security/CVE-2020-7063

Affected software / configurations for CVE-2020-7063

Vendor Product Version Raw CPE
php php >= 7.2.0, <= 7.2.27 cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
php php >= 7.3.0, <= 7.3.14 cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
php php >= 7.4.0, <= 7.4.2 cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
tenable tenable.sc < 5.19.0 cpe:2.3:a:tenable:tenable.sc:*:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
opensuse leap 15.1 cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*

References for CVE-2020-7063

cvelogic Threat Intelligence