CVE-2019-16317 Pimcore RCE via PHAR upload

High 8.8 Published Updated

An attacker with limited privileges can execute arbitrary code by uploading a malicious PHAR file and triggering its deserialization via a phar:// URL.

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 CVE-2019-16317?

CVE-2019-16317 is a high-severity unsafe deserialization vulnerability in Pimcore Pimcore, published on 14 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-502

Which versions are affected by CVE-2019-16317?

2 open source packages ship an affected version, including pimcore/pimcore. It affects 1 product.

PackageAffectedFixed in
pimcore/pimcore PackagistAll versions5.7.1
pimcore/pimcore PackagistAll versions5.7.1

Products include Pimcore Pimcore.

How do I fix CVE-2019-16317?

Upgrade pimcore/pimcore to 5.7.1 or later.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2019-16317 being exploited?

There is no known exploitation of CVE-2019-16317 in the wild and no public exploit code.

All Pimcore Pimcore vulnerabilities

Sources

Also known as GHSA-352x-hc2f-fwff, SNYK-PHP-PIMCOREPIMCORE-451599.

Is CVE-2019-16317 in your software?

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

Check your SBOMs for free