Browse cwe weaknesses with official CWE context and Glexia analysis.
Search And Filters
Showing 50 of 969 CWE records · Page 11 of 20.
The product uses a database table that includes records that should not be accessible to an actor, but it executes a SQL statement with a primary key that can be controlled by that actor.
The product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes.
The product contains a finalize() method that does not call super.finalize().
The product contains an expression that will always evaluate to false.
The product contains an expression that will always evaluate to true.
The product calls a thread's run() method instead of calling start(), which causes the code to run in the thread of the caller instead of the callee.
The product does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform.
The product violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.
The product violates the Enterprise JavaBeans (EJB) specification by using AWT/Swing.
The product violates the Enterprise JavaBeans (EJB) specification by using the java.io package.
The product violates the Enterprise JavaBeans (EJB) specification by using sockets.
The product violates the Enterprise JavaBeans (EJB) specification by using the class loader.
The product stores a non-serializable object as an HttpSession attribute, which can hurt reliability.
The product contains a clone() method that does not call super.clone() to obtain the new object.
The product does not maintain equal hashcodes for equal objects.
The product declares an array public, final, and static, which is not sufficient to prevent the array's contents from being modified.
The product violates secure coding principles for mobile code by declaring a finalize() method public.
The code has a return statement inside a finally block, which will cause any thrown exception in the try block to be discarded.
The product contains an empty synchronized block.
The product makes an explicit call to the finalize() method from outside the finalizer.
The product sets a pointer to a specific address other than NULL or 0.
Casting a non-structure type to a structure type and accessing a field can lead to memory access errors or data corruption.
The product uses an API function that does not exist on all versions of the target platform. This could cause portability problems or inconsistencies that allow denial of service or other consequences.
The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().
The product stores sensitive data in memory that is not locked, or that has been incorrectly locked, which might cause the memory to be written to swap files on disk by the virtual memory manager. This can make the data more accessible to external actors.
This weakness has been deprecated because it covered redundant concepts already described in CWE-287.
The product modifies the SSL context after connection creation has begun.
When the J2EE container attempts to write unserializable objects to disk there is no guarantee that the process will complete successfully.
The product compares object references instead of the contents of the objects themselves, preventing it from detecting equivalent objects.
This weakness has been deprecated. It was poorly described and difficult to distinguish from other entries. It was also inappropriate to assign a separate ID solely because of domain-specific considerations. Its closest equivalent is CWE-1023.
The product uses the wrong operator when comparing a string, such as using "==" when the .equals() method should be used instead.
The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.
The product uses OpenSSL and trusts or uses a certificate without using the SSL_get_verify_result() function to ensure that the certificate satisfies all necessary security requirements.
The Servlet does not catch all exceptions, which may reveal sensitive debugging information.
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.
A client/server product performs authentication within client code but not in server code, allowing server-side authentication to be bypassed via a modified client that omits the authentication check.
When multiple sockets are allowed to bind to the same port, other services on that port may be stolen or spoofed.
The product does not properly check inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.
A public or protected static final field references a mutable object, which allows the object to be changed by malicious code, or accidentally from another package.
An ActionForm class contains a field that has not been declared private, which can be accessed without using a setter or getter.
The product uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient.
The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
The product creates a search index of private or sensitive documents, but it does not properly limit index access to actors who are authorized to see the original information.
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
The Secure attribute for sensitive cookies in HTTPS sessions is not set.
While adding general comments is very useful, some programmers tend to leave important data, such as: filenames related to the web application, old links or links which were not meant to be browsed by users, old code fragments, etc.
The PHP application uses an old method for processing uploaded files by referencing the four global variables that are set for each file (e.g. $varname, $varname_size, $varname_name, $varname_type). These variables could be overwritten by attackers, causing the application to process unauthorized files.
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
