CVE-2019-16317
First published: Sat Sep 14 2019(Updated: )
In Pimcore before 5.7.1, an attacker with limited privileges can trigger execution of a .phar file via a `phar://` URL in a filename parameter, because PHAR uploads are not blocked and are reachable within the `phar://../../../../../../../../var/www/html/web/var/assets/` directory, a different vulnerability than CVE-2019-10867 and CVE-2019-16318.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| composer/pimcore/pimcore | <5.7.1 | 5.7.1 |
| Pimcore E-commerce Framework | <5.7.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-16317?
CVE-2019-16317 is considered a high severity vulnerability due to the potential for remote code execution.
How do I fix CVE-2019-16317?
To fix CVE-2019-16317, upgrade Pimcore to version 5.7.1 or later.
What causes CVE-2019-16317?
CVE-2019-16317 is caused by the lack of blocking for PHAR file uploads, allowing attackers to exploit the system using crafted filenames.
Who is affected by CVE-2019-16317?
CVE-2019-16317 affects all versions of Pimcore prior to 5.7.1.
What can an attacker do with CVE-2019-16317?
An attacker with limited privileges can execute arbitrary PHP code by triggering a .phar file upload.
- collector/github-advisory-latest
- alias/GHSA-352x-hc2f-fwff
- alias/CVE-2019-16317
- collector/github-advisory
- agent/author
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/remedy
- agent/weakness
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-cve
- package-manager/composer
- vendor/pimcore
- canonical/pimcore e-commerce framework