GHSA-9895-26wr-4fgv: EZsystems Remote code execution in file uploads
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.7.2, 2019.3.4.2, 5.4.14.1.
Low priority for now. Upgrade to ezsystems/ezpublish-legacy (Packagist) 2017.12.7.2, 2019.3.4.2, 5.4.14.1 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
This Security Advisory is about a vulnerability in the way eZ Platform and eZ Publish Legacy handles file uploads, which can in the worst case lead to remote code execution (RCE), a very serious threat. An attacker would need access to uploading files to be able to exploit the vulnerability, so if you have strict controls on this and trust all who have this permission, you're not affected. On the basis of the tests we have made, we also believe the vulnerability cannot be exploited as long as our recommended vhost configuration is used. Here is the v2.5 recommendation for Nginx, as an example: https://github.com/ezsystems/ezplatform/blob/2.5/doc/nginx/vhost.template#L31 This vhost template specifies that only the file app.php in the web root is executed, while vulnerable configurations allow execution of any php file. Apache is affected in the same way as Nginx, and is also protected by using the recommended configuration. The build-in webserver in PHP stays vulnerable, as it doesn't use this type of configuration (this webserver should only be used for development, never for production). We cannot be 100% certain our configuration is not vulnerable. We also do not know if all our users use the recommended configuration, so we send out this fix to be on the safe side. The fix includes a blacklist feature for uploaded filenames, such as ".php". The file types on the blacklist cannot be uploaded. The blacklist is configurable. In eZ Platform you will find it as ezsettings.default.io.file_storage.file_type_blacklist in eZ/Bundle/EzPublishCoreBundle/Resources/config/default_settings.yml in vendors/ezsystems/ezpublish-kernel. In eZ Publish Legacy you will find it as FileExtensionBlackList in settings/file.ini. By default it blocks these file types: php, php3, phar, phpt, pht, phtml, pgif. The fix also inclues a new block against path traversal attacks, though this kind of attack was not reproducible in our tests.
- Published
- May 15, 2024
- Updated
- Nov 29, 2024
- EPSS
- —
- CWE
- CWE-94
Report tools
Action score
0
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| Packagist | ezsystems/ezpublish-legacy | pkg:composer/ezsystems/ezpublish-legacy |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | ezsystems/ezpublish-legacy | from 2017.12.0 · before 2017.12.7.2 | 2017.12.7.2 |
| Packagist | ezsystems/ezpublish-legacy | from 2019.3.0 · before 2019.3.4.2 | 2019.3.4.2 |
| Packagist | ezsystems/ezpublish-legacy | from 5.4.0 · before 5.4.14.1 | 5.4.14.1 |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-39j2-4p9j-5w4jEz Platform Object Injection in legacy shop module0Monitor
- GHSA-pqjm-xcp8-wgmmEz Platform and Legacy are prone to an insecure interpretation of PHP/PHAR uploads0Monitor
- GHSA-p9mp-vq4v-v5m5eZ Publish Legacy Passwordless login for LDAP users0Monitor
Published before and after this one in the same product
- ← EarlierGHSA-cc2j-92jq-wgjgMay 15, 2024 · eZ Publish Information disclosure in backend content tree menu0Monitor
- ← EarlierGHSA-82rv-45pc-v28wMay 15, 2024 · eZ Publish Legacy Patch EZSA-2018-001 for Several vulnerabilities0Monitor
- ← EarlierGHSA-2vh3-cj9j-mcj5May 15, 2024 · eZ Publish Legacy Cross-site Scripting (XSS) in 'disabled module' error template0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:ezsystems/ezpublish-legacy | 2017.12.7.2 | Package registry (OSV) |
| Packagist:ezsystems/ezpublish-legacy | 2019.3.4.2 | Package registry (OSV) |
| Packagist:ezsystems/ezpublish-legacy | 5.4.14.1 | Package 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- GHSA-39j2-4p9j-5w4j0 days apartEz Platform Object Injection in legacy shop module0Monitor
- GHSA-pqjm-xcp8-wgmm0 days apartEz Platform and Legacy are prone to an insecure interpretation of PHP/PHAR uploads0Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (2)
- Fix✗ → ✓
- CVSS8 → —
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.