HexBrain

Nextcloud · Report #145495

nextcloud.com: Directory listening for 'wp-includes' forders

Validstatus
4upvotes
17 Jun 2016disclosed

How it was found

Hello guys,

Details: The web server is configured to display the list of files contained in this directory. As a result of a misconfiguration - end user / attacker able to see content of the folders with systemically important files

Vulnerable place: /wp-includes directory

when I tried to navigate to this directory via your domain - service responses me 'Access forbidden', but if I will navigate to the same directory via IP address (http://88.198.160.129/) - service will reflects whole entry.

PoC: {F100046}

Impact: Exposing the contents of a directory can lead to an attacker gaining access to source code or providing useful information for the attacker to devise exploits, such as creation times of files or any information that may be encoded in file names. The directory listing may also compromise private or confidential data.

Remediation:

  • Configure your web server to prevent directory listings for all paths beneath the web root;
  • Place into each directory a default file (such as index.htm) that the web server will display instead of returning a directory listing.

Let me know if you have any question.

Thanks for your attention, Stas

This report was disclosed publicly on HackerOne and belongs to its author and the program. See the original