Top 10 2010-A7-Insecure Cryptographic Storage - Revision history

Wichers at 16:14, 24 October 2011

2011-10-24T16:14:53Z

Wichers at 03:31, 6 May 2010

2010-05-06T03:31:05Z

Neil Smithline at 14:59, 1 May 2010

2010-05-01T14:59:30Z

Neil Smithline at 01:02, 29 April 2010

2010-04-29T01:02:18Z

Neil Smithline at 22:01, 23 April 2010

2010-04-23T22:01:12Z

Wichers at 17:38, 22 April 2010

2010-04-22T17:38:57Z

Wichers at 16:41, 22 April 2010

2010-04-22T16:41:18Z

Wichers at 16:21, 22 April 2010

2010-04-22T16:21:15Z

Neil Smithline at 20:04, 21 April 2010

2010-04-21T20:04:55Z

Neil Smithline at 20:03, 21 April 2010

2010-04-21T20:03:03Z

@@ Line 2: / Line 2: @@
 {{Top_10_2010:SummaryTableHeaderBeginTemplate}}
-{{Top_10_2010:SummaryTableValue-1-Template|Exploitability|EASY}}
+{{Top_10_2010:SummaryTableValue-3-Template|Exploitability|DIFFICULT}}
-{{Top_10_2010:SummaryTableValue-2-Template|Prevalence|COMMON}}
+{{Top_10_2010:SummaryTableValue-3-Template|Prevalence|UNCOMMON}}
-{{Top_10_2010:SummaryTableValue-2-Template|Detectability|DIFFICULT}}
+{{Top_10_2010:SummaryTableValue-3-Template|Detectability|DIFFICULT}}
-{{Top_10_2010:SummaryTableValue-0-Template|Impact|SEVERE}}
+{{Top_10_2010:SummaryTableValue-1-Template|Impact|SEVERE}}
 {{Top_10_2010:SummaryTableHeaderEndTemplate}}
       <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate}}>Consider the users of your system. Would they like to gain access to protected data they aren’t authorized for? What about internal administrators?</td>

@@ Line 37: / Line 37: @@
 {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|number=4|risk=7}}
 {{Top_10_2010:SubSubsectionOWASPReferencesTemplate}}
 For a more complete set of requirements and problems to avoid in this area, see the [http://www.owasp.org/index.php/ASVS#tab=Downloads ASVS requirements on Cryptography (V7)].
 * [[Top_10_2007-Insecure_Cryptographic_Storage | OWASP Top 10-2007 on Insecure Cryptographic Storage]]

@@ Line 1: / Line 1: @@
 {{Top_10_2010:TopTemplate|useprev=2010PrevLink|usenext=2010NextLink|prev=A6-Security Misconfiguration|next=A8-Failure to Restrict URL Access}}
-<center>
-{| style="align:center; text-align:center; border:2px solid #4F81BD; background-color:#F2F2F2; padding=2;"
+{{Top_10_2010:SummaryTableHeaderBeginTemplate}}
-|- style="background-color: #4F81Bd; color: #FFFFFF;"
+{{Top_10_2010:SummaryTableValue-1-Template|Exploitability|EASY}}
-! width="16.5%" | Threat Agents
+{{Top_10_2010:SummaryTableValue-2-Template|Prevalence|COMMON}}
-! width="16.5%" | Attack Vectors
+{{Top_10_2010:SummaryTableValue-2-Template|Detectability|DIFFICULT}}
-! width="33%" colspan="2" | Security Weakness
+{{Top_10_2010:SummaryTableValue-0-Template|Impact|SEVERE}}
-! width="16.5%" | Technical Impacts
+{{Top_10_2010:SummaryTableHeaderEndTemplate}}
-! width="16.5%" | Business Impacts
+     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate}}>Consider the users of your system. Would they like to gain access to protected data they aren’t authorized for? What about internal administrators?</td>
-|-
+     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate}}>Attackers typically don’t break the crypto. They break something else, such as find keys, get cleartext copies of data, or access data via channels that automatically decrypt.
-| style="background-color: #D9D9D9; color: #000000;" | ______
+</td>
-| style="background-color: #FF0000; color: #000000;" | '''Exploitability<br>EASY
+     <td colspan=2  {{Template:Top 10 2010:SummaryTableRowStyleTemplate}}>The most common flaw in this area is simply not encrypting data that deserves encryption. When encryption is employed, unsafe key generation and storage, not rotating keys, and weak algorithm usage is common. Use of weak or unsalted hashes to protect passwords is also common. External attackers have difficulty detecting such flaws due to limited access. They usually must exploit something else first to gain the needed access.</td>
-| style="background-color: #FFFF00; color: #000000;" | '''Prevalence<br>UNCOMMON
+     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate}}>Failure frequently compromises all data that should have been encrypted. Typically this information includes sensitive data such as health records, credentials, personal data, credit cards, etc.</td>
-| style="background-color: #FFB200; color: #000000;" | '''Detectability<br>DIFFICULT
+     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate}}>Consider the business value of the lost data and impact to your reputation. What is your legal liability if this data is exposed? Also consider the damage to your reputation.</td>
-| style="background-color: #FF0000; color: #000000;" | '''Impact<br>SEVERE
+{{Top_10_2010:SummaryTableEndTemplate}}
-| style="background-color: #D9D9D9; color: #000000;" | ______
 {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|number=1|risk=7}}
 The first thing you have to determine is which data is sensitive enough to require encryption. For example, passwords, credit cards, health records, and personal information should be encrypted. For all such data, ensure:

@@ Line 23: / Line 23: @@
 |}
 </center>
-{{Top_10_2010:SubsectionVulnerableTemplate|Insecure Cryptographic Storage|
+{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|number=1|risk=7}}
 The first thing you have to determine is which data is sensitive enough to require encryption. For example, passwords, credit cards, health records, and personal information should be encrypted. For all such data, ensure:
 # It is encrypted everywhere it is stored long term, particularly in backups of this data.
@@ Line 30: / Line 30: @@
 #A strong key is generated, protected from unauthorized access, and key change is planned for.
 And more ... For a more complete set of problems to avoid, see the [[ASVS | ASVS requirements on Cryptography (V7)]].
-}}
+{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|number=2|risk=7}}
 The full perils of unsafe cryptography are well beyond the scope of this Top 10. That said, for all sensitive data deserving encryption, do all of the following, at a minimum:
 # Considering the threats you plan to protect this data from (e.g., insider attack, external user), make sure you encrypt all such data at rest in a manner that defends against these threats.
@@ Line 38: / Line 37: @@
 # Ensure passwords are hashed with a strong standard algorithm and an appropriate salt is used.
 # Ensure all keys and passwords are protected from unauthorized access.
-}}
+{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|number=3|risk=7}}
 '''Scenario #1''': An application encrypts credit cards in a database to prevent exposure to end users. However, the database is set to automatically decrypt queries against the credit card columns, allowing an SQL injection flaw to retrieve all the credit cards in cleartext. The system should have been configured to allow only back end applications to decrypt them, not the front end web application.
@@ Line 45: / Line 43: @@
 '''Scenario #3''': The password database uses unsalted hashes to store everyone’s passwords. A file upload flaw allows an attacker to retrieve the password file. All the unsalted hashes can be brute forced in 4 weeks, while properly salted hashes would have taken over 3000 years.
-}}
+{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|number=4|risk=7}}
 {{Top_10_2010:SubSubsectionOWASPReferencesTemplate}}
 For a more complete set of requirements and problems to avoid in this area, see the [http://www.owasp.org/index.php/ASVS#tab=Downloads ASVS requirements on Cryptography (V7)].
@@ Line 57: / Line 54: @@
 * [http://cwe.mitre.org/data/definitions/312.html CWE Entry 312 on Cleartext Storage of Sensitive Information]
 * [http://cwe.mitre.org/data/definitions/326.html CWE Entry 326 on Weak Encryption]
-{{Top_10_2010:BottomTemplate|useprev=2010PrevLink|usenext=2010NextLink|prev=A6-Security Misconfiguration|next=A8-Failure to Restrict URL Access}}
+{{Top_10_2010:BottomAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|useprev=2010PrevLink|usenext=2010NextLink|prev=A6-Security Misconfiguration|next=A8-Failure to Restrict URL Access}}
 [[Category:OWASP Top Ten Project]]

@@ Line 3: / Line 3: @@
 {| style="align:center; text-align:center; border:2px solid #4F81BD; background-color:#F2F2F2; padding=2;"
 |- style="background-color: #4F81Bd; color: #FFFFFF;"
-! Threat Agents !! Attack Vectors
+! width="16.5%" | Threat Agents
-! colspan="2" | Security Weakness
+! width="16.5%" | Attack Vectors
-! Technical Impacts
+! width="33%" colspan="2" | Security Weakness
-! Business Impacts
+! width="16.5%" | Technical Impacts
 |-
 | style="background-color: #D9D9D9; color: #000000;" | ______
@@ Line 14: / Line 15: @@
 | style="background-color: #FF0000; color: #000000;" | '''Impact<br>SEVERE
 | style="background-color: #D9D9D9; color: #000000;" | ______
-|-
+|-valign="top"
 | style="text-align: left; border: 2px solid #FFFFFF;" | Consider the users of your system. Would they like to gain access to protected data they aren’t authorized for? What about internal administrators?
 | style="text-align: left; border: 2px solid #FFFFFF;" | Attackers typically don’t break the crypto. They break something else, such as find keys, get cleartext copies of data, or access data via channels that automatically decrypt.

← Older revision		Revision as of 17:38, 22 April 2010
Line 57:		Line 57:
	* [http://cwe.mitre.org/data/definitions/326.html CWE Entry 326 on Weak Encryption]		* [http://cwe.mitre.org/data/definitions/326.html CWE Entry 326 on Weak Encryption]
	{{Top_10_2010:BottomTemplate\|useprev=2010PrevLink\|usenext=2010NextLink\|prev=A6-Security Misconfiguration\|next=A8-Failure to Restrict URL Access}}		{{Top_10_2010:BottomTemplate\|useprev=2010PrevLink\|usenext=2010NextLink\|prev=A6-Security Misconfiguration\|next=A8-Failure to Restrict URL Access}}
		+
		+	[[Category:OWASP Top Ten Project]]

@@ Line 39: / Line 39: @@
 }}
 {{Top_10_2010:SubsectionExampleTemplate|Insecure Cryptographic Storage|
-'''Scenario #''': An application encrypts credit cards in a database to prevent exposure to end users. However, the database is set to automatically decrypt queries against the credit card columns, allowing an SQL injection flaw to retrieve all the credit cards in cleartext. The system should have been configured to allow only back end applications to decrypt them, not the front end web application.
+'''Scenario #1''': An application encrypts credit cards in a database to prevent exposure to end users. However, the database is set to automatically decrypt queries against the credit card columns, allowing an SQL injection flaw to retrieve all the credit cards in cleartext. The system should have been configured to allow only back end applications to decrypt them, not the front end web application.
 '''Scenario #2''': A backup tape is made of encrypted health records, but the encryption key is on the same backup. The tape never arrives at the backup center.

@@ Line 2: / Line 2: @@
 <center>
 {| style="align:center; text-align:center; border:2px solid #4F81BD; background-color:#F2F2F2; padding=2;"
-|- style="background-color: #4F81Bd; color: #000000;"
+|- style="background-color: #4F81Bd; color: #FFFFFF;"
 ! Threat Agents !! Attack Vectors
 ! colspan="2" | Security Weakness
@@ Line 8: / Line 8: @@
 ! Business Impacts
 |-
-| style="background-color: #D9D9D9; color: #FFFFFF;" | ______
+| style="background-color: #D9D9D9; color: #000000;" | ______
-| style="background-color: #FF0000; color: #FFFFFF;" | Exploitability<br>EASY
+| style="background-color: #FF0000; color: #000000;" | Exploitability<br>EASY
-| style="background-color: #FFFF00; color: #FFFFFF;" | Prevalence<br>UNCOMMON
+| style="background-color: #FFFF00; color: #000000;" | Prevalence<br>UNCOMMON
-| style="background-color: #FFB200; color: #FFFFFF;" | Detectability<br>DIFFICULT
+| style="background-color: #FFB200; color: #000000;" | Detectability<br>DIFFICULT
-| style="background-color: #FF0000; color: #FFFFFF;" | Impact<br>SEVERE
+| style="background-color: #FF0000; color: #000000;" | Impact<br>SEVERE
-| style="background-color: #D9D9D9; color: #FFFFFF;" | ______
+| style="background-color: #D9D9D9; color: #000000;" | ______
 |-
 | style="text-align: left; border: 2px solid #FFFFFF;" | Consider the users of your system. Would they like to gain access to protected data they aren’t authorized for? What about internal administrators?