CWE-1055: Multiple Inheritance from Concrete Classes
The product contains a class with inheritance from more than one concrete class.
Browse cwe weaknesses with official CWE context and Glexia analysis.
Search And Filters
Showing 50 of 969 CWE records · Page 16 of 20.
The product contains a class with inheritance from more than one concrete class.
A named-callable or method control element has a signature that supports a variable (variadic) number of parameters or arguments.
The product uses a dedicated, central data manager component as required by design, but it contains code that performs data-access operations that do not use this data manager.
The code contains a function or method that operates in a multi-threaded environment but owns an unsafe non-final static storable or member data element.
The product does not contain sufficient technical or engineering documentation (whether on paper or in electronic form) that contains descriptions of all the relevant software/hardware elements of the product, such as its usage, structure, architectural components, interfaces, design, implementation, configuration, operation, etc.
The product performs too many data queries without using efficient data processing functionality such as stored procedures.
The product does not sufficiently hide the internal representation and implementation details of data or methods, which might allow external components or modules to modify data unexpectedly, invoke unexpected functionality, or introduce dependencies that the programmer did not intend.
The code has a parent class that contains references to a child class, its methods, or its members.
A static code block creates an instance of a class.
The product contains a function, subroutine, or method whose signature has an unnecessarily large number of parameters/arguments.
The product uses deployed components from application servers, but it also uses low-level functions/methods for management of resources, instead of the API provided by the application server.
The product contains a serializable data element that does not have an associated serialization method.
The product contains a data query against an SQL table or view that is configured in a way that does not utilize an index and may cause sequential searches to be performed.
The implementation of the product is not consistent with the design as described within the relevant documentation.
An invokable code block contains an exception handling block that does not contain any code, i.e. is empty.
The product contains a serializable, storable data element such as a field or member, but the data element contains member elements that are not serializable.
The source code contains a block that does not contain any code, i.e., the block is empty.
The product accesses a data resource through a database without using a connection pooling capability.
The product contains a client with a function or method that contains a large number of data accesses/queries that are sent through a data manager, i.e., does not use efficient database capabilities.
A class has an inheritance level that is too high, i.e., it has a large number of parent classes.
The product performs unconditional control transfer (such as a "goto") in code outside of a branching structure such as a switch block.
The product's architecture, source code, design, documentation, or other artifact does not follow required conventions.
The code performs a comparison such as an equality test between two float (floating point) values, but it uses comparison operators that do not account for the possibility of loss of precision.
The source code does not follow desired style or formatting for indentation, white space, comments, etc.
A parent class contains one or more child classes, but the parent class does not have a virtual destructor method.
A source code file has too many lines of code.
The code contains a class instance that calls the method or function to delete or destroy itself.
The product is intended to manage data access through a particular data manager component such as a relational or non-SQL database, but it contains code that performs data access operations without using that component.
A function or method contains too many operations that utilize a data manager or file resource.
A function, method, procedure, etc. contains an excessive amount of code that has been commented out within its body.
A class contains an unnecessarily large number of children.
A class contains a virtual method, but the method does not have an associated virtual destructor.
The code has a synchronous call to a remote resource, but there is no timeout for the call, or the timeout is set to infinite.
The product uses a large data table that contains an excessively large number of indices.
A method for a class performs an operation that directly accesses a member element from another class.
The product contains a method that accesses an object but does not later invoke the element's associated finalize/destructor method.
The product uses the same control element across multiple architectural layers.
The product uses an unnecessarily complex internal representation for its data structures or interrelationships between those structures.
The product contains an index range scan for a large data table, but the scan can cover a large number of rows.
The product uses a loop with a control flow condition based on a value that is updated within the body of the loop.
The product 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.
The product uses a storable data element that does not have all of the associated functions or methods that are necessary to support comparison.
The code contains a data element with a pointer that does not have an associated copy or constructor method.
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.
The product or code does not isolate system-dependent functionality into separate standalone modules.
The product uses automatically-generated code that cannot be executed without a specific runtime support component.
The code uses a data representation that relies on low-level data representation or constructs that may vary across different processors, physical machines, OSes, or other physical components.
The product relies on third-party components that do not provide equivalent functionality across all desirable platforms.
The product relies on third-party components that are not actively supported or maintained by the original developer or a trusted proxy for the original developer.
The product or code uses machine-dependent functionality, but it does not sufficiently encapsulate or isolate this functionality from the rest of the code.