Information Exposure Through Comments
|ID: 615||Date: (C)2012-05-14 (M)2012-11-08|
|Type: weakness||Status: INCOMPLETE|
|Abstraction Type: Variant|
While adding general comments is very useful, some programmers
tend to leave important data, such as: filenames related to the web application,
old links or links which were not meant to be browsed by users, old code
Extended DescriptionAn attacker who finds these comments can map the application's structure
and files, expose hidden parts of the site, and study the fragments of code
to reverse engineer the application, which may help develop further attacks
against the site.
Time Of Introduction
|Confidentiality ||Read application
data || |
|Distribution || ||Remove comments which have sensitive information about the
design/implementation of the application. Some of the comments may be
exposed to the user and affect the security posture of the
application. || || |
|CWE-615 ChildOf CWE-895 ||Category ||CWE-888 || |
Demonstrative Examples (Details)
- The following comment, embedded in a JSP, will be displayed in the
resulting HTML output.
- CVE-2007-6197 : Version numbers and internal hostnames leaked in HTML comments.
- CVE-2007-4072 : CMS places full pathname of server in HTML comment.
- CVE-2009-2431 : blog software leaks real username in HTML comment.
For more examples, refer to CVE relations in the bottom box.
White Box Definitions None
Black Box Definitions None