You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use WebRCE for this one. Regarding ports, I think we have a list of webports that we try for all web exploits. If drupal has a unique default port then add it to config, but as far as scanning goes, we only need custom scanner if the actual exploit attempt takes a long time.
FWIW, to set up a vulnerable Drupal server I used this tutorial, and made sure the following modules are installed (in the Drupal UI Extend menu):
REST Web Services
HTTP Basic Authentication
Node
For experimenting with the exploit quoted in this issue, you need to be acquainted with clearing cache, which is done from Configuration > Performance menu.
Running the exploit looks like that:
PS C:\Users\ophir.harpaz\Desktop\Guardicore\monkey\drupal> python .\cve-2019-6340.py http://172.23.74.255/ id
CVE-2019-6340 Drupal 8 REST Services Unauthenticated RCE PoC
by @leonjza
References:
https://www.drupal.org/sa-core-2019-003
https://www.ambionics.io/blog/drupal8-rce
[warning] Caching heavily affects reliability of this exploit.
Nodes are used as they are discovered, but once they are done,
you will have to wait for cache expiry.
Targetting http://172.23.74.255/...
[+] Finding a usable node id...
[+] Using node_id 1
requesting http://172.23.74.255/node/1
[+] Target appears to be vulnerable!
uid=33(www-data) gid=33(www-data) groups=33(www-data)
Activity
ophirharpazg commentedon Jun 14, 2020
WebRCEorHostExploiter)Some more things:
VakarisZ commentedon Jun 15, 2020
Use
WebRCEfor this one. Regarding ports, I think we have a list of webports that we try for all web exploits. If drupal has a unique default port then add it to config, but as far as scanning goes, we only need custom scanner if the actual exploit attempt takes a long time.ophirharpazg commentedon Aug 10, 2020
FWIW, to set up a vulnerable Drupal server I used this tutorial, and made sure the following modules are installed (in the Drupal UI
Extendmenu):For experimenting with the exploit quoted in this issue, you need to be acquainted with clearing cache, which is done from
Configuration>Performancemenu.Running the exploit looks like that:
ophirharpazg commentedon Aug 27, 2020
VakarisZ commentedon Aug 28, 2020
Nice! But icons tell me that you need to backmerge