Vulnerability Description
In Pimcore before 5.7.1, an attacker with limited privileges can bypass file-extension restrictions via a 256-character filename, as demonstrated by the failure of automatic renaming of .php to .php.txt for long filenames, a different vulnerability than CVE-2019-10867 and CVE-2019-16317.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Pimcore | Pimcore | < 5.7.1 |
Related Weaknesses (CWE)
References
- https://github.com/pimcore/pimcore/commit/732f1647cc6e0a29b5b1f5d904b4d726b5e945Patch
- https://snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-451598Third Party Advisory
- https://github.com/pimcore/pimcore/commit/732f1647cc6e0a29b5b1f5d904b4d726b5e945Patch
- https://snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-451598Third Party Advisory
FAQ
What is CVE-2019-16318?
CVE-2019-16318 is a vulnerability with a CVSS score of 8.8 (HIGH). In Pimcore before 5.7.1, an attacker with limited privileges can bypass file-extension restrictions via a 256-character filename, as demonstrated by the failure of automatic renaming of .php to .php.t...
How severe is CVE-2019-16318?
CVE-2019-16318 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2019-16318?
Check the references section above for vendor advisories and patch information. Affected products include: Pimcore Pimcore.