Pimcore up to 5.7.0 PHAR File filename deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Pimcore up to 5.7.0. Affected is an unknown function of the component PHAR File Handler. Such manipulation of the argument filename leads to deserialization. This vulnerability is referenced as CVE-2019-16317. It is possible to launch the attack remotely. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Pimcore up to 5.7.0 and classified as critical. Affected by this issue is an unknown functionality of the component PHAR File Handler. The manipulation of the argument filename with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was published 09/14/2019. This vulnerability is handled as CVE-2019-16317 since 09/14/2019. The exploitation is known to be easy. The attack may be launched remotely. The successful exploitation needs a simple authentication. There are known technical details, but no exploit is available.
Upgrading to version 5.7.1 eliminates this vulnerability.
Similar entry is available at VDB-141801. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
License
Website
- Product: https://github.com/pimcore/pimcore/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Pimcore 5.7.1
Patch: github.com
Timeline
09/14/2019 🔍09/14/2019 🔍
09/15/2019 🔍
12/25/2023 🔍
Sources
Product: github.comAdvisory: 6ee5d8536d0802e377594cbe39083e822710aab9
Status: Not defined
CVE: CVE-2019-16317 (🔍)
GCVE (CVE): GCVE-0-2019-16317
GCVE (VulDB): GCVE-100-141800
See also: 🔍
Entry
Created: 09/15/2019 08:24Updated: 12/25/2023 09:11
Changes: 09/15/2019 08:24 (38), 09/15/2019 08:29 (17), 12/25/2023 09:11 (6)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.