Skip to content
Noroxi
OSV ecosystem advisory

GHSA-pqjm-xcp8-wgmm: Ez Platform and Legacy are prone to an insecure interpretation of PHP/PHAR uploads

Medium—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Fixed version: ezsystems/ezpublish-legacy (Packagist) 2017.12.4.3, 2018.6.1.4, 2018.9.1.3.

Low priority for now. Upgrade to ezsystems/ezpublish-legacy (Packagist) 2017.12.4.3, 2018.6.1.4, 2018.9.1.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

The eZ Platform and Legacy are affected by an issue related to how uploaded PHP and PHAR files are handled, and consists of two parts: 1. Web server configuration, and 2. Disabling the PHAR stream wrapper. **1. WEB SERVER CONFIGURATION** The sample web server configuration in our documentation can in some cases allow the execution of uploaded PHP/PHAR code. This can be abused to allow priviledge escalation and breach of content access controls, among other things. Please ensure that your web server will not execute files in directories were files may be uploaded, such as web/var/ and ezpublish_legacy/var/ As an example, here is how you can make Apache return HTTP 403 Forbidden for a number of executable file types in your eZ Platform var directory. Please adapt it to your needs. It is then possible to enable logging of HTTP 403 in a separate log file if you wish, you could do this to see if someone is trying to abuse the server. ``` RewriteEngine On # disable .php(3) and other extensions in the var directory RewriteRule ^var/.*(?i)\.(php3?|phar|phtml|sh|exe|pl|bin)$ - [F] ``` Here is the same configuration, but for the Nginx web server: ``` location ~ ^/var/.*(?i)\.(php3?|phar|phtml|sh|exe|pl|bin)$ { return 403; } ``` **2. DISABLE PHAR STREAM WRAPPER** PHAR archives may be crafted such that its stream wrapper will execute them without being specifically asked to. With such files, any PHP file operation may cause deserialisation and execution. This may happen even if the file name suffix isn't ".phar". Any site that allows file uploads is at risk. Normally eZ Platform has no need for PHAR support. It's only used by Composer, and that is executed separately from eZ Platform. So one way to avoid this vulnerability is to disable the PHAR stream wrapper within eZ Platform. (If you know you need PHAR support, please consider other means to deal with this vulnerability. For example, enabling the wrapper only in those scripts/bundles that have to deal with such files.) Disabling the stream wrapper should be done in: eZ Platform (web/app.php) CLI scripts (bin/console) Legacy (index.php and CLI scripts) To install, use Composer to update to one of the "Resolving versions" mentioned above, or apply these patches manually: https://github.com/ezsystems/ezplatform/commit/9a0c52dc4535e4b3ce379f80222dc53f705a2cfd https://github.com/ezsystems/ezpublish-legacy/commit/d21957bf202b091ab39dfb5be300f6c30be3933e

Published
May 15, 2024
Updated
Nov 29, 2024
EPSS
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-pqjm-xcp8-wgmm

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Packagistezsystems/ezpublish-legacy

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistezsystems/ezpublish-legacyfrom 2011.0.0 · before 2017.12.4.32017.12.4.3
Packagistezsystems/ezpublish-legacyfrom 2018.6.0 · before 2018.6.1.42018.6.1.4
Packagistezsystems/ezpublish-legacyfrom 2018.9.0 · before 2018.9.1.32018.9.1.3
Packagistezsystems/ezpublish-legacyfrom 5.3.0 · before 5.3.12.65.3.12.6
Packagistezsystems/ezpublish-legacyfrom 5.4.0 · before 5.4.12.35.4.12.3

Other highest-scoring records for the same primary product.

Published before and after this one in the same product

  • ← EarlierGHSA-cc2j-92jq-wgjgMay 15, 2024 · eZ Publish Information disclosure in backend content tree menu
    0Monitor
  • ← EarlierGHSA-82rv-45pc-v28wMay 15, 2024 · eZ Publish Legacy Patch EZSA-2018-001 for Several vulnerabilities
    0Monitor
  • ← EarlierGHSA-2vh3-cj9j-mcj5May 15, 2024 · eZ Publish Legacy Cross-site Scripting (XSS) in 'disabled module' error template
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Packagist:ezsystems/ezpublish-legacy2017.12.4.3Package registry (OSV)
Packagist:ezsystems/ezpublish-legacy2018.6.1.4Package registry (OSV)
Packagist:ezsystems/ezpublish-legacy2018.9.1.3Package registry (OSV)
Packagist:ezsystems/ezpublish-legacy5.3.12.6Package registry (OSV)
Packagist:ezsystems/ezpublish-legacy5.4.12.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

Not on record for this CVE: EPSS history · researcher credit · public bounty program.

Technical details

References

All records