StackHawk Documentation StackHawk Logo HawkDocs

No results found

Try different keywords or check your spelling

Search documentation

Find guides, API references, and more

esc
Back to Index

Information Disclosure - Suspicious Comments

Reference
Plugin ID: 10027 WASC: 13 Unknown Passive Information Leakage

Remediation

  1. Remove development comments: Strip all development, debugging, and TODO comments from production code before deployment.
  2. Review comment content: Audit all comments for sensitive information like passwords, database connection strings, or system details.
  3. Implement build processes: Use automated build processes to remove comments and minimize code before production deployment.
  4. Sanitize error messages: Ensure error messages and debugging information don't contain sensitive details.
  5. Regular code review: Conduct periodic code reviews to identify and remove any accidentally committed sensitive comments.

About

Suspicious comments in web applications can reveal sensitive information such as development notes, system details, passwords, debugging information, or business logic that could assist attackers. These comments often remain in production code unintentionally, providing valuable reconnaissance information to malicious actors.

Risks

Low Suspicious comments can provide attackers with insights into application architecture, potential vulnerabilities, or sensitive information that may facilitate targeted attacks or system reconnaissance.

Your privacy settings

We use first and third party cookies to ensure that we give you the best experience on our website and in our products.