PHPRAP up to 1.0.8 debug.php api[url] server-side request forgery

Summaryinfo

A vulnerability marked as critical has been reported in PHPRAP 1.0.4/1.0.5/1.0.6/1.0.7/1.0.8. Affected by this vulnerability is an unknown functionality of the file application/home/controller/debug.php. This manipulation of the argument api[url] as part of POST Request causes server-side request forgery. This vulnerability is tracked as CVE-2018-11031. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability classified as critical was found in PHPRAP 1.0.4/1.0.5/1.0.6/1.0.7/1.0.8. Affected by this vulnerability is an unknown code of the file application/home/controller/debug.php. The manipulation of the argument api[url] as part of a POST Request leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

application/home/controller/debug.php in PHPRAP 1.0.4 through 1.0.8 has SSRF via the /debug URI, as demonstrated by an api[url]=file:////etc/passwd&api[method]=get POST request.

The bug was discovered 05/11/2018. The weakness was disclosed 05/14/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2018-11031 since 05/13/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:application/home/controller/debug.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.

The entry VDB-117668 is pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• PHPRAP

Version

• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion