Difference between revisions of "Hard-Coded Password"

From OWASP
Jump to: navigation, search
(Related Vulnerabilities)
Line 1: Line 1:
 
{{Template:Stub}}
 
{{Template:Stub}}
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
 
+
<br>
__TOC__
+
  
 
[[ASDR Table of Contents]]
 
[[ASDR Table of Contents]]

Revision as of 21:25, 17 February 2009

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.


This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.



ASDR Table of Contents

Last revision (mm/dd/yy): 02/17/2009

Description

A hard-coded password vulnerability occurs when usernames and passwords are included in HTML comments. Because HTML comments are not displayed, it was often the mentality that normal users would not see them. It can also occur when a specific username (usually unique) does not require a password.

Risk Factors

TBD

Examples

This example shows how usernames and passwords can be included within HTML comments:

<form name="login" action="login.php" method="post" onSubmit="return email_Submit();">
    <b>Log in Address: </b>
    <input type="text" name="email" size="29" value="">
    <b>Password: </b>
    <input type="password" name="password" size="29" value="">

<!-- Debugging credentials: wiki@owasp.org:abc123 -->

</form>

Related Attacks


Related Vulnerabilities

Related Controls

Related Technical Impacts


References

TBD