Skip to main content

Configuration Alerts

Open Directory (opendir)

What is it?
A web server misconfiguration that allows visitors to browse directory contents (e.g., /files/) instead of being restricted to specific web pages.

Where is it detected?

  • Detected during vulnerability scans, penetration tests, or manual browsing of URL paths.

  • Commonly flagged by tools like Nessus, Burp Suite, or Nikto.

Alert lvl:
⚠️ Medium – Can expose sensitive files and aid in targeted attacks.

  • Disable directory listing.

  • Store sensitive files outside web-accessible directories.

  • Conduct regular audits of file paths exposed to the internet.

PHP Error Display

What is it?
When PHP error messages are displayed directly in the browser instead of being hidden and logged securely.

Where is it detected?

  • Detected during penetration tests, vulnerability scans, or by simply triggering errors on the site (e.g., malformed requests).

Alert lvl:
⚠️ Medium – Reveals internal system details (file paths, queries, API keys) that attackers can exploit.

  • Disable display_errors in production environments.

  • Log errors to a secure server or file instead of displaying them publicly.

  • Implement custom error pages for users.

  • Regularly review logs for abnormal or repeated errors.

Public Config

What is it?
Files, databases, or storage resources are accidentally configured as “public,” making them accessible without authentication.

Where is it detected?

  • Detected during cloud security audits, vulnerability scans, or penetration tests.

  • Common with cloud storage (e.g., AWS S3, Azure Blob, Google Cloud Storage).

Alert lvl:
❗ High – Often leads to large-scale data leaks and breaches.

  • Apply “private by default” permissions to all storage resources.

  • Review access controls regularly (especially in cloud environments).

  • Use encryption and authentication for all sensitive files.

  • Enable monitoring for unauthorized public access changes.

Security Header Config

What is it?
Missing or misconfigured HTTP response headers that strengthen browser-level protections against attacks.

Where is it detected?

  • Detected using automated tools such as securityheaders.com, OWASP ZAP, or penetration testing.
  • Common headers include CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.

Alert lvl:
⚠️ Medium – Increases exposure to XSS, clickjacking, and MITM attacks.

, OWASP ZAP, or penetration testing.Common headers include CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.

    • Add and properly configure key security headers.

    • Follow OWASP Secure Headers Project guidelines.

    • Regularly test site headers with automated tools.

    • Review headers after web server or app updates.


For more information, please check the following article:
https://blog.projectdiscovery.io/guide-to-dns-takeovers/ 

Back to top