Difference between revisions of "Password Management: Weak Cryptography"

From OWASP
Jump to: navigation, search
 
(2 intermediate revisions by one user not shown)
Line 1: Line 1:
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
 
{{Template:Fortify}}
 
{{Template:Fortify}}
 
__TOC__
 
 
[[ASDR Table of Contents]]
 
  
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
 
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+
  
  
Line 38: Line 33:
  
 
This code will run successfully, but anyone with access to config.properties can read the value of password and easily determine that the value has been base 64 encoded. If a devious employee has access to this information, they can use it to break into the system.
 
This code will run successfully, but anyone with access to config.properties can read the value of password and easily determine that the value has been base 64 encoded. If a devious employee has access to this information, they can use it to break into the system.
 +
*You can harden with letters, numbers and symbols, Hermetic Password against dictionary attacks, letters and even brute force script used by crackers to steal identities, bank accounts, mails, administrators.
 +
The following combinations you can create:
 +
¢J{B}/aK0]EY=\÷7|\8%\*)A>¡#(W|a
 +
¢30=÷7|852-42-----*
 +
#¢m3Tr¡¢d38r¡Sr3m4k3
 +
Scripture charmap.exe:: Tw Cent Condensed Extra Bold::encrypt passwords with AES http://axantum.com/axcrypt
  
 
==Related [[Attacks]]==
 
==Related [[Attacks]]==

Latest revision as of 11:59, 13 September 2010

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


This article includes content generously donated to OWASP by Fortify.JPG.

Last revision (mm/dd/yy): 09/13/2010

Vulnerabilities Table of Contents


Description

Obscuring a password with a trivial encoding does not protect the password.

Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. A programmer can attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password.

Risk Factors

TBD


Examples

The following code reads a password from a properties file and uses the password to connect to a database.

	...
	Properties prop = new Properties();
	prop.load(new FileInputStream("config.properties"));
	String password = Base64.decode(prop.getProperty("password"));
	
	DriverManager.getConnection(url, usr, password);
	...

This code will run successfully, but anyone with access to config.properties can read the value of password and easily determine that the value has been base 64 encoded. If a devious employee has access to this information, they can use it to break into the system.

  • You can harden with letters, numbers and symbols, Hermetic Password against dictionary attacks, letters and even brute force script used by crackers to steal identities, bank accounts, mails, administrators.

The following combinations you can create: ¢J{B}/aK0]EY=\÷7|\8%\*)A>¡#(W|a ¢30=÷7|852-42-----*

  1. ¢m3Tr¡¢d38r¡Sr3m4k3

Scripture charmap.exe:: Tw Cent Condensed Extra Bold::encrypt passwords with AES http://axantum.com/axcrypt

Related Attacks


Related Vulnerabilities

Related Controls


Related Technical Impacts


References

TBD