This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Dead Code: Unused Method"
From OWASP
Line 4: | Line 4: | ||
− | |||
− | |||
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' |
Revision as of 23:29, 7 April 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 04/7/2009
Description
This method is never called or is only called from other dead code.
Risk Factors
TBD
Examples
Example 1
In the following class, the method doWork() can never be called.
public class Dead { private void doWork() { System.out.println("doing work"); } public static void main(String[] args) { System.out.println("running Dead"); } }
Example 2
In the following class, two private methods call each other, but since neither one is ever invoked from anywhere else, they are both dead code.
public class DoubleDead { private void doTweedledee() { doTweedledumb(); } private void doTweedledumb() { doTweedledee(); } public static void main(String[] args) { System.out.println("running DoubleDead"); } }
(In this case it is a good thing that the methods are dead: invoking either one would cause an infinite loop.)
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
TBD