Difference between revisions of "Failure to provide confidentiality for stored data"

From OWASP
Jump to: navigation, search
(Reverting to last version not containing links to www.textlaaler.com)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
 +
{{Template:Vulnerability}}
  
==Overview==
+
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
Non-final public fields should be avoided, if possible, as the code is easily tamperable.
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
  
==Consequences ==
+
==Description==
  
* Integrity: The object could potentially be tampered with.
+
Non-final public fields should be avoided, if possible, as the code is easily tamperable.
  
* Confidentiality: The object could potentially allow the object to be read.
+
'''Consequences'''
  
==Exposure period ==
+
* Integrity: The object could potentially be tampered with.
 +
* Confidentiality: The object could potentially allow the object to be read.
  
* Implementation: This flaw is a simple logic issue, introduced entirely at implementation time.
+
'''Exposure period'''
  
==Platform ==
+
* Implementation: This flaw is a simple logic issue, introduced entirely at implementation time.
  
* Languages: Java, C++
+
'''Platform'''
  
* Operating platforms: Any
+
* Languages: Java, C++
 +
* Operating platforms: Any
  
==Required resources ==
+
'''Required resources'''
  
 
Any
 
Any
  
==Severity ==
+
'''Severity'''
  
 
Medium
 
Medium
  
==Likelihood   of exploit ==
+
'''Likelihood of exploit'''
  
 
High
 
High
  
==Avoidance and mitigation ==
 
  
* Implementation: Make any non-final field private.
+
If a field is non-final and public, it can be changed once their value is set by any function which has access to the class which contains the field.
  
==Discussion ==
 
  
If a field is non-final and public, it can be changed once their value is set by any function which has access to the class which contains the field.
+
==Risk Factors==
  
==Examples ==
+
TBD
 +
 
 +
==Examples==
  
 
In C++:
 
In C++:
Line 57: Line 60:
 
Now this field is readable from any function and can be changed by any function.
 
Now this field is readable from any function and can be changed by any function.
  
==Related problems ==
 
  
Not available.
+
==Related [[Attacks]]==
  
 +
* [[Attack 1]]
 +
* [[Attack 2]]
  
[[Category:Vulnerability]]
 
  
[[Category:General Logic Errors]]
+
==Related [[Vulnerabilities]]==
  
 +
* [[Vulnerability 1]]
 +
* [[Vulnerabiltiy 2]]
 +
 +
 +
==Related [[Controls]]==
 +
 +
* Implementation: Make any non-final field private.
 +
 +
 +
==Related [[Technical Impacts]]==
 +
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
 +
 +
 +
==References==
 +
TBD
 +
 +
[[Category:FIXME|add links
 +
 +
In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
 +
 +
Availability Vulnerability
 +
 +
Authorization Vulnerability
 +
 +
Authentication Vulnerability
 +
 +
Concurrency Vulnerability
 +
 +
Configuration Vulnerability
 +
 +
Cryptographic Vulnerability
 +
 +
Encoding Vulnerability
 +
 +
Error Handling Vulnerability
 +
 +
Input Validation Vulnerability
 +
 +
Logging and Auditing Vulnerability
 +
 +
Session Management Vulnerability]]
 +
 +
__NOTOC__
 +
 +
 +
[[Category:OWASP ASDR Project]]
 +
[[Category:Vulnerability]]
 +
[[Category:General Logic Error Vulnerability]]
 
[[Category:OWASP_CLASP_Project]]
 
[[Category:OWASP_CLASP_Project]]

Latest revision as of 13:29, 27 May 2009

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


Last revision (mm/dd/yy): 05/27/2009

Vulnerabilities Table of Contents

Description

Non-final public fields should be avoided, if possible, as the code is easily tamperable.

Consequences

  • Integrity: The object could potentially be tampered with.
  • Confidentiality: The object could potentially allow the object to be read.

Exposure period

  • Implementation: This flaw is a simple logic issue, introduced entirely at implementation time.

Platform

  • Languages: Java, C++
  • Operating platforms: Any

Required resources

Any

Severity

Medium

Likelihood of exploit

High


If a field is non-final and public, it can be changed once their value is set by any function which has access to the class which contains the field.


Risk Factors

TBD

Examples

In C++:

public int password r = 45;

In Java:

public String r = new String("My Password");

Now this field is readable from any function and can be changed by any function.


Related Attacks


Related Vulnerabilities


Related Controls

  • Implementation: Make any non-final field private.


Related Technical Impacts


References

TBD