32%
18%
23%
A vulnerability classified as problematic has been found in Linux Kernel. Affected is the function j1939_session_destroy of the file net/can/j1939/transport.c of the component IPsec. The manipulation leads to memory leak. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211932.
CVSS 3.1 Base Score 3.3. CVSS Attack Vector: local. CVSS Attack Complexity: low. CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L).
The following method never closes the file handle it opens. The Finalize() method for StreamReader eventually calls Close(), but there is no guarantee as to how long it will take before the Finalize() method is invoked. In fact, there is no guarantee that Finalize() will ever be invoked. In a busy environment, this can result in the VM using up all of its available file handles.
}}processLine(line);This code attempts to open a connection to a database and catches any exceptions that may occur.
}Connection con = DriverManager.getConnection(some_connection_string);log( e );If an exception occurs after establishing the database connection and before the same connection closes, the pool of database connections may become exhausted. If the number of available connections is exceeded, other users cannot access this resource, effectively denying access to the application.
Under normal conditions the following C# code executes a database query, processes the results returned by the database, and closes the allocated SqlConnection object. But if an exception occurs while executing the SQL or processing the results, the SqlConnection object is not closed. If this happens often enough, the database will run out of available cursors and not be able to execute any more SQL queries.
...The following C function does not close the file handle it opens if an error occurs. If the process is long-lived, the process can run out of file handles.
}
return DECODE_SUCCESS;return DECODE_FAIL;
}}return DECODE_FAIL;decodeBlock(buf);In this example, the program does not use matching functions such as malloc/free, new/delete, and new[]/delete[] to allocate/deallocate the resource.
}void foo();delete ptr;In this example, the program calls the delete[] function on non-heap memory.
}void foo(bool);delete[] p;11,22p = new int[2];The following C function leaks a block of allocated memory if the call to read() does not return the expected number of bytes:
}
return buf;return NULL;
return NULL;ExploitPedia is constantly evolving. Sign up to receive a notification when we release additional functionality.
If you'd like to report a bug or have any suggestions for improvements then please do get in touch with us using this form. We will get back to you as soon as we can.