Difference between revisions of "Overflow of static internal buffer"

From OWASP
Jump to: navigation, search
(Examples)
Line 1: Line 1:
 
  
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
Line 68: Line 67:
  
 
[[Category:Synchronization and Timing Errror]]
 
[[Category:Synchronization and Timing Errror]]
 +
 +
[[Category:OWASP_CLASP_Project]]

Revision as of 12:32, 16 May 2006


Overview

A non-final static field can be viewed and edited in dangerous ways.

Consequences

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

Exposure period

  • Design through Implementation: This is a simple logical issue which can be easily remedied through simple protections.

Platform

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

Required resources

Any

Severity

Medium

Likelihood of exploit

High

Avoidance and mitigation

  • Design through Implementation: Make any static fields private and final.

Discussion

Non-final fields, which are not public can be read and written to by arbitrary Java code.

Examples

In C++:

public int password r = 45;

In Java:

static public String r;

This is a uninitiated static class which can be accessed without a get-accessor and changed without a set-accessor.

Related problems

Not available.

Categories