Pydio up to 8.2.2 pydio-core proxy.php hash unrestricted upload

Summaryinfo

A vulnerability classified as critical was found in Pydio up to 8.2.2. Impacted is an unknown function of the file proxy.php of the component pydio-core. Executing a manipulation of the argument hash with the input ../../../../../var/lib/pydio/data/personal/guest/PoC.php as part of PHP File can lead to unrestricted upload. This vulnerability appears as CVE-2019-9642. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability classified as critical was found in Pydio up to 8.2.2. This vulnerability affects an unknown function of the file proxy.php of the component pydio-core. The manipulation of the argument hash with the input value ../../../../../var/lib/pydio/data/personal/guest/PoC.php leads to a unrestricted upload vulnerability. The CWE definition for the vulnerability is CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

An issue was discovered in proxy.php in pydio-core in Pydio through 8.2.2. Through an unauthenticated request, it possible to evaluate malicious PHP code by placing it on the fourth line of a .php file, as demonstrated by a PoC.php created by the guest account, with execution via a proxy.php?hash=../../../../../var/lib/pydio/data/personal/guest/PoC.php request. This is related to plugins/action.share/src/Store/ShareStore.php.

The weakness was presented 06/05/2019 (Website). The advisory is shared for download at pydio.com. This vulnerability was named CVE-2019-9642 since 03/09/2019. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1608.002.

By approaching the search of inurl:proxy.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Pydio

Version

• 8.2.0
• 8.2.1
• 8.2.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion