 |
VOOZH | about |
|
VOOZH | about |
A community-developed list of SW & HW weaknesses that can become vulnerabilities
CWE-1041: Use of Redundant Code
View customized information:
For users who are interested in more notional aspects of a weakness. Example: educators, technical writers, and project/program managers.
For users who are concerned with the practical application and details about the nature of a weakness and how to prevent it from happening. Example: tool developers, security researchers, pen-testers, incident response analysts.
For users who are mapping an issue to CWE/CAPEC IDs, i.e., finding the most appropriate CWE for a specific issue (e.g., a CVE record). Example: tool developers, security researchers.
For users who wish to see all available information for the CWE/CAPEC entry.
For users who want to customize what details are displayed.
×
Edit Custom Filter
👁 +
Description The product has multiple functions, methods, procedures, macros, etc. that
contain the same code.
👁 +
Common Consequences 👁 Section Help
This table specifies different individual consequences associated with the weakness. The Scope identifies the application security area that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in exploiting this weakness. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a weakness will be exploited to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact.
👁 +
Potential Mitigations
👁 +
Relationships
👁 Section Help
This table shows the weaknesses and high level categories that are related to this weakness. These relationships are defined as ChildOf, ParentOf, MemberOf and give insight to similar items that may exist at higher and lower levels of abstraction. In addition, relationships such as PeerOf and CanAlsoBe are defined to show similar weaknesses that the user may want to explore.
👁 +
Relevant to the view "Research Concepts" (View-1000)
👁 +
Relevant to the view "Software Development" (View-699)
👁 +
Modes Of Introduction 👁 Section Help
The different Modes of Introduction provide information about how and when this weakness may be introduced. The Phase identifies a point in the life cycle at which introduction may occur, while the Note provides a typical scenario related to introduction during the given phase.
👁 +
Applicable Platforms 👁 Section Help
This listing shows possible areas for which the given weakness could appear. These may be for specific named Languages, Operating Systems, Architectures, Paradigms, Technologies, or a class of such platforms. The platform is listed along with how frequently the given weakness appears for that instance.
👁 +
Demonstrative Examples Example 1 In the following Java example the code performs some complex math when specific test conditions are met. The math is the same in each case and the equations are repeated within the code. Unfortunately if a future change needs to be made then that change needs to be made in all locations. This opens the door to mistakes being made and the changes not being made in the same way in each instance. (bad code)
Example Language: Java
public class Main {
public static void main(String[] args) {
double s = 10.0;
double r = 1.0; double pi = 3.14159; double surface_area; if(r > 0.0) { // complex math equations
surface_area = pi * r * s + pi * Math.pow(r, 2); } if(r > 1.0) { // a complex set of math
surface_area = pi * r * s + pi * Math.pow(r, 2); } } } It is recommended to place the complex math into its own function and then call that function whenever necessary. (good code)
Example Language: Java
public class Main {
private double ComplexMath(double r, double s) {
//complex math equations
double pi = Math.PI; double surface_area = pi * r * s + pi * Math.pow(r, 2); return surface_area; } public static void main(String[] args) {
double s = 10.0;
double r = 1.0; double surface_area; if(r > 0.0) { surface_area = ComplexMath(r, s);
} if(r > 1.0) { surface_area = ComplexMath(r, s);
} } } 👁 +
Weakness Ordinalities
👁 +
Detection Methods
👁 +
Memberships
👁 Section Help
This MemberOf Relationships table shows additional CWE Categories and Views that reference this weakness as a member. This information is often useful in understanding where a weakness fits within the context of external information sources.
👁 +
Vulnerability Mapping Notes
👁 +
Taxonomy Mappings
👁 +
References
👁 +
Content History
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
