You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Deprecated methods should not be used in new code. Refer to the complete list of deprecated APIs available in the Java SE 6 documentation. [[API 06]].

The guideline CON01-J. Avoid using ThreadGroup APIs describes issues that can result from using deprecated methods.

A class is obsolete if it is unofficially deprecated. For example, the java.util.Dictionary class provides the same functionality as the Map interface and is generally outmoded. The java.util.Calendar class suffers from multi-threading related issues and so does its subclasses, such as, java.util.GregorianCalendar. Similarly, all the subclasses of the abstract class java.text.Format are thread-unsafe. These classes must be avoided in multi-threaded code.

Risk Assessment

Using deprecated methods in program code can lead to unexpected, ill-defined behavior.

Rule

Severity

Likelihood

Remediation Cost

Priority

Level

MET36-J

high

likely

medium

P18

L1

Automated Detection

TODO

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

References

[[API 06]] Deprecated API
[[SDN 08]] Bug database, Bug ID 4264153
[[MITRE 09]] CWE ID 589


MET35-J. Ensure that the clone method calls super.clone      12. Methods (MET)      MET37-J. Do not call overridable methods from a privileged block

  • No labels