All posts by rocco

CWE-1096 – Singleton Class Instance Creation without Proper Locking or Synchronization

Read Time:15 Second

Description

The software implements a Singleton design pattern but does not use appropriate locking or other synchronization mechanism to ensure that the singleton class is only instantiated once.

Modes of Introduction:

 

 

Related Weaknesses

CWE-820
CWE-662
CWE-662

 

Consequences

Other: Reduce Reliability

 

Potential Mitigations

CVE References

CWE-1097 – Persistent Storable Data Element without Associated Comparison Control Element

Read Time:14 Second

Description

The software uses a storable data element that does not have
all of the associated functions or methods that are necessary to support
comparison.

Modes of Introduction:

 

 

Related Weaknesses

CWE-1076
CWE-595

 

Consequences

Other: Reduce Reliability

 

Potential Mitigations

CVE References

CWE-1099 – Inconsistent Naming Conventions for Identifiers

Read Time:15 Second

Description

The product’s code, documentation, or other artifacts do not
consistently use the same naming conventions for variables, callables, groups of
related callables, I/O capabilities, data types, file names, or similar types of
elements.

Modes of Introduction:

 

 

Related Weaknesses

CWE-1078

 

Consequences

 

Potential Mitigations

CVE References

CWE-11 – ASP.NET Misconfiguration: Creating Debug Binary

Read Time:51 Second

Description

Debugging messages help attackers learn about the system and plan a form of attack.

ASP .NET applications can be configured to produce debug binaries. These binaries give detailed debugging messages and should not be used in production environments. Debug binaries are meant to be used in a development or testing environment and can pose a security risk if they are deployed to production.

The debug attribute of the tag defines whether compiled binaries should include debugging information. The use of debug binaries causes an application to provide as much information about itself as possible to the user.

Modes of Introduction:

– Implementation

 

 

Related Weaknesses

CWE-489

 

Consequences

Confidentiality: Read Application Data

Attackers can leverage the additional information they gain from debugging output to mount attacks targeted on the framework, database, or other resources used by the application.

 

Potential Mitigations

Phase: System Configuration

Description: 

Avoid releasing debug binaries into the production environment. Change the debug mode to false when the application is deployed into production.

CVE References