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

From OWASP
Jump to: navigation, search
Line 1: Line 1:
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 
 
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
  
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
+
__TOC__
  
 
[[ASDR Table of Contents]]
 
[[ASDR Table of Contents]]
__TOC__
 
  
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 +
 +
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
  
 
==Description==
 
==Description==

Revision as of 08:21, 2 November 2008

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


Contents


ASDR Table of Contents

Last revision (mm/dd/yy): 11/2/2008

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