Difference between revisions of "Hard-Coded Password"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
 +
 +
{{Template:Stub}}
 +
 +
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 +
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 +
 +
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 +
 +
[[ASDR Table of Contents]]
 +
__TOC__
 +
  
 
==Description==
 
==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.
 
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.
  
==Examples ==
+
==Risk Factors==
===Example 1===
+
 
 +
TBD
 +
 
 +
==Examples==
 +
 
 
This example shows how usernames and passwords can be included within HTML comments:
 
This example shows how usernames and passwords can be included within HTML comments:
  
Line 18: Line 35:
 
</form></pre>
 
</form></pre>
  
===Example 2===
+
==Related [[Attacks]]==
  
==Related Threats==
+
* [[Attack 1]]
 +
* [[Attack 2]]
  
==Related Attacks==
 
  
==Related Vulnerabilities==
+
==Related [[Vulnerabilities]]==
 +
 
 
* [[Information Leak (information disclosure)]]
 
* [[Information Leak (information disclosure)]]
 
* [[Infoleak Using Debug Information]]
 
* [[Infoleak Using Debug Information]]
  
==Related Countermeasures==
 
  
[[:Category:Authentication]]
+
==Related [[Controls]]==
  
==Categories==
+
* [[:Category:Authentication]]
  
 +
==Related [[Technical Impacts]]==
 +
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
 +
 +
 +
==References==
 +
 +
TBD
 +
__NOTOC__
 +
 +
 +
[[Category:OWASP ASDR Project]]
 
[[Category:Password Management Vulnerability]]
 
[[Category:Password Management Vulnerability]]
 
[[Category:Authentication Vulnerability]]
 
[[Category:Authentication Vulnerability]]
 
[[Category:Sensitive Data Protection Vulnerability]]
 
[[Category:Sensitive Data Protection Vulnerability]]
{{Template:Stub}}
 

Revision as of 07:14, 25 September 2008

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


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

Last revision (mm/dd/yy): 09/25/2008

Vulnerabilities Table of Contents

ASDR Table of Contents

Contents


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