• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Forwarded to devs Possible disclosure of information: .htaccess accessible through nginx

Sergio Manzi

Regular Pleskian
TITLE:
Possible disclosure of information: .htaccess accessible through nginx
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk 17.8.10 (upgraded from 17.5.3#40)
CentOS 7.4.1708, Kernel 3.10.0-693
PROBLEM DESCRIPTION:
Possible disclosure of information:
  • You have a site running under Apache having a .htaccess file in its root (or several of them in other directories)
  • You re-configure that site to "Nginx-Only" hosting
  • You forget to delete the .htaccess files
  • The .htaccess files are accessible (like e.g.: https://www.example.com/.htaccess)
STEPS TO REPRODUCE:
  • Have a site having a .htaccess file at its root and running under Apache
  • Try to access that file from a browser
  • You get an error 403 (Forbidden)
  • Transition the site to Nginx-only hosting
  • Try to access .htaccess again
ACTUAL RESULT:
You are "served" the .htaccess file and you can save it locally​
EXPECTED RESULT:
Refusal to serve the file as a precaution (possible disclosure of sensible information)​
ANY ADDITIONAL INFORMATION:
I appreciate that the responsibility of the site content is under the user, but I think in a similar scenario it would be wise to have nginx automatically configured to refuse access to .htaccess files
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Thank you for report.
Bugreport PPPM-8063 was created.
 
Back
Top