CVE-2019-16317: High severity pimcore e-commerce framework vulnerability
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.
Other sources
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.
Affected Software
Remediation
Event History
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.