Categories
CWE | NAME | LAST 12M | LOW | MEDIUM | HIGH | CRITICAL | TOTAL VULNS |
---|---|---|---|---|---|---|---|
CWE-913 | Improper Control of Dynamically-Managed Code Resources The software does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements. | 0 | 10 | 16 | 15 | 41 | |
CWE-565 | Reliance on Cookies without Validation and Integrity Checking The application relies on the existence or values of cookies when performing security-critical operations, but it does not properly ensure that the setting is valid for the associated user. | 2 | 14 | 14 | 10 | 40 | |
CWE-669 | Incorrect Resource Transfer Between Spheres The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource. | 0 | 11 | 20 | 8 | 39 | |
CWE-672 | Operation on a Resource after Expiration or Release The software uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. | 1 | 17 | 15 | 4 | 37 | |
CWE-693 | Protection Mechanism Failure The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. | 1 | 18 | 12 | 4 | 35 | |
CWE-388 | 7PK - Errors This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that occur when an application does not properly handle errors that occur during processing. According to the authors of the Seven Pernicious Kingdoms, "Errors and error handling represent a class of API. Errors related to error handling are so common that they deserve a special kingdom of their own. As with 'API Abuse,' there are two ways to introduce an error-related security vulnerability: the most common one is handling errors poorly (or not at all). The second is producing errors that either give out too much information (to possible attackers) or are difficult to handle." | 0 | 11 | 11 | 12 | 34 | |
CWE-320 | Key Management Errors Weaknesses in this category are related to errors in the management of cryptographic keys. | 1 | 12 | 15 | 6 | 34 | |
CWE-93 | Improper Neutralization of CRLF Sequences ('CRLF Injection') The software uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs. | 0 | 24 | 6 | 0 | 30 | |
CWE-335 | Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG) The software uses a Pseudo-Random Number Generator (PRNG) that does not correctly manage seeds. | 0 | 3 | 13 | 8 | 24 | |
CWE-470 | Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') The application uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code. | 0 | 3 | 14 | 7 | 24 |