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

Not scored Published

Attackers can execute arbitrary code via uploaded PHP/PHAR files if web server configuration allows execution in upload directories or PHAR stream wrapper is enabled.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is GHSA-pqjm-xcp8-wgmm?

GHSA-pqjm-xcp8-wgmm is a code injection vulnerability in ezsystems/ezpublish-legacy, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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

Which versions are affected by GHSA-pqjm-xcp8-wgmm?

10 open source packages ship an affected version, including ezsystems/ezpublish-legacy.

PackageAffectedFixed in
ezsystems/ezpublish-legacy PackagistFrom 2011.0.02017.12.4.3
ezsystems/ezpublish-legacy PackagistFrom 2011.0.02017.12.4.3
ezsystems/ezpublish-legacy PackagistFrom 2018.6.02018.6.1.4
ezsystems/ezpublish-legacy PackagistFrom 2018.6.02018.6.1.4
ezsystems/ezpublish-legacy PackagistFrom 2018.9.02018.9.1.3
ezsystems/ezpublish-legacy PackagistFrom 2018.9.02018.9.1.3
4 more packages
ezsystems/ezpublish-legacy PackagistFrom 5.3.05.3.12.6
ezsystems/ezpublish-legacy PackagistFrom 5.3.05.3.12.6
ezsystems/ezpublish-legacy PackagistFrom 5.4.05.4.12.3
ezsystems/ezpublish-legacy PackagistFrom 5.4.05.4.12.3

How do I fix GHSA-pqjm-xcp8-wgmm?

Upgrade ezsystems/ezpublish-legacy to a fixed version for your release line: 2017.12.4.3, 2018.6.1.4, 2018.9.1.3 or 5.3.12.6.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is GHSA-pqjm-xcp8-wgmm being exploited?

There is no known exploitation of GHSA-pqjm-xcp8-wgmm in the wild and no public exploit code.

Sources

Is GHSA-pqjm-xcp8-wgmm in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free