| # | CWE | Nom | Résumé | Voir aussi | Nombre |
|---|
| 1 | CWE-79 | Cross Site Scripting | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. | CWE-94 | 35316 |
| 2 | CWE-119 | Memory Corruption | The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. | | 25410 |
| 3 | CWE-200 | Information Disclosure | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. | CWE-284 | 19232 |
| 4 | CWE-89 | SQL Injection | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. | CWE-74 | 17389 |
| 5 | CWE-404 | Denial of Service | The product does not release or incorrectly releases a resource before it is made available for re-use. | | 13525 |
| 6 | CWE-20 | Improper Input Validation | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. | | 10946 |
| 7 | CWE-264 | Improper Access Controls | | | 8306 |
| 8 | CWE-284 | Improper Access Controls | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. | CWE-266 | 8203 |
| 9 | CWE-269 | Improper Privilege Management | The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. | CWE-266 | 7890 |
| 10 | CWE-352 | Cross-Site Request Forgery | The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. | CWE-862 | 7504 |
| 11 | CWE-22 | Path Traversal | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. | | 7335 |
| 12 | CWE-125 | Out-of-Bounds Read | The product reads data past the end, or before the beginning, of the intended buffer. | CWE-119 | 6333 |
| 13 | CWE-416 | Use After Free | Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. | CWE-119 | 5972 |
| 14 | CWE-80 | Basic Cross Site Scripting | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. | CWE-74 | 5826 |
| 15 | CWE-287 | Improper Authentication | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. | | 4751 |
| 16 | CWE-787 | Out-of-bounds Write | The product writes data past the end, or before the beginning, of the intended buffer. | CWE-119 | 4386 |
| 17 | CWE-94 | Code Injection | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. | CWE-74 | 4269 |
| 18 | CWE-399 | Improper Resource Management | | CWE-404 | 3961 |
| 19 | CWE-476 | NULL Pointer Dereference | A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. | CWE-404 | 3953 |
| 20 | CWE-121 | Stack-based Buffer Overflow | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). | CWE-119 | 3755 |
| 21 | CWE-120 | Buffer Overflow | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. | CWE-119 | 3540 |
| 22 | CWE-77 | Command Injection | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. | CWE-74 | 3268 |
| 23 | CWE-862 | Missing Authorization | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. | CWE-863 | 2951 |
| 24 | CWE-310 | Cryptographic Issues | | | 2915 |
| 25 | CWE-434 | Unrestricted Upload | The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. | CWE-284 | 2882 |
| 26 | CWE-78 | OS Command Injection | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. | CWE-77 | 2743 |
| 27 | CWE-122 | Heap-based Buffer Overflow | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). | CWE-119 | 2458 |
| 28 | CWE-190 | Integer Overflow | The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. | CWE-189 | 2257 |
| 29 | CWE-400 | Resource Consumption | The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. | CWE-404 | 2250 |
| 30 | CWE-502 | Deserialization | The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. | CWE-20 | 2152 |
| 31 | CWE-275 | Permission Issues | | CWE-266 | 1905 |
| 32 | CWE-73 | File Inclusion | The product allows user input to control or influence paths or file names that are used in filesystem operations. | | 1703 |
| 33 | CWE-74 | Injection | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. | CWE-707 | 1595 |
| 34 | CWE-918 | Server-Side Request Forgery | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. | | 1543 |
| 35 | CWE-189 | Numeric Error | | | 1507 |
| 36 | CWE-362 | Race Condition | The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. | | 1490 |
| 37 | CWE-285 | Improper Authorization | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. | CWE-266 | 1374 |
| 38 | CWE-255 | Credentials Management | | | 1305 |
| 39 | CWE-611 | XML External Entity Reference | 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. | CWE-610 | 1289 |
| 40 | CWE-601 | Open Redirect | A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. | | 1158 |
| 41 | CWE-798 | Hard-coded Credentials | The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. | CWE-259 | 1037 |
| 42 | CWE-295 | Improper Certificate Validation | The product does not validate, or incorrectly validates, a certificate. | CWE-287 | 994 |
| 43 | CWE-254 | 7PK Security Features | | | 978 |
| 44 | CWE-401 | Memory Leak | The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. | CWE-404 | 881 |
| 45 | CWE-59 | Link Following | The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. | | 835 |
| 46 | CWE-426 | Untrusted Search Path | The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control. | | 813 |
| 47 | CWE-863 | Incorrect Authorization | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. | CWE-285 | 794 |
| 48 | CWE-532 | Sensitive Information in Log Files | Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. | CWE-200 | 731 |
| 49 | CWE-311 | Missing Encryption of Sensitive Data | The product does not encrypt sensitive or critical information before storage or transmission. | CWE-310 | 667 |
| 50 | CWE-61 | Symlink Following | The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. | CWE-59 | 665 |
| 51 | CWE-427 | Uncontrolled Search Path | The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors. | CWE-426 | 664 |
| 52 | CWE-290 | Authentication Bypass by Spoofing | This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. | CWE-287 | 650 |
| 53 | CWE-770 | Allocation of Resources | The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. | CWE-400 | 619 |
| 54 | CWE-276 | Incorrect Default Permissions | During installation, installed file permissions are set to allow anyone to modify those files. | CWE-266 | 599 |
| 55 | CWE-306 | Missing Authentication | The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. | CWE-287 | 590 |
| 56 | CWE-134 | Format String | The product uses a function that accepts a format string as an argument, but the format string originates from an external source. | CWE-119 | 574 |
| 57 | CWE-415 | Double Free | The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. | CWE-119 | 556 |
| 58 | CWE-843 | Type Confusion | The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. | | 520 |
| 59 | CWE-835 | Infinite Loop | The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. | CWE-404 | 512 |
| 60 | CWE-732 | Incorrect Permission Assignment | The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. | CWE-275 | 477 |
| 61 | CWE-312 | Cleartext Storage of Sensitive Information | The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. | CWE-310 | 475 |
| 62 | CWE-371 | State Issue | | | 472 |
| 63 | CWE-639 | Authorization Bypass | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. | CWE-285 | 456 |
| 64 | CWE-19 | Data Processing Error | | | 446 |
| 65 | CWE-319 | Cleartext Transmission of Sensitive Information | The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. | CWE-310 | 438 |
| 66 | CWE-522 | Insufficiently Protected Credentials | The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. | | 417 |
| 67 | CWE-665 | Improper Initialization | The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. | | 395 |
| 68 | CWE-347 | Improper Verification of Cryptographic Signature | The product does not verify, or incorrectly verifies, the cryptographic signature for data. | CWE-345 | 387 |
| 69 | CWE-824 | Uninitialized Pointer | The product accesses or uses a pointer that has not been initialized. | CWE-908 | 384 |
| 70 | CWE-326 | Inadequate Encryption Strength | The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. | CWE-310 | 371 |
| 71 | CWE-16 | Configuration | | | 366 |
| 72 | CWE-912 | Backdoor | The product contains functionality that is not documented, not part of the specification, and not accessible through an interface or command sequence that is obvious to the product's users or administrators. | | 345 |
| 73 | CWE-129 | Improper Validation of Array Index | The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. | CWE-119 | 344 |
| 74 | CWE-617 | Reachable Assertion | 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. | | 336 |
| 75 | CWE-21 | Pathname Traversal (deprecated) | | CWE-22 | 331 |
| 76 | CWE-345 | Insufficient Verification of Data Authenticity | The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. | | 331 |
| 77 | CWE-369 | Divide By Zero | The product divides a value by zero. | CWE-404 | 328 |
| 78 | CWE-209 | Information Exposure Through Error Message | The product generates an error message that includes sensitive information about its environment, users, or associated data. | CWE-200 | 312 |
| 79 | CWE-307 | Improper Restriction of Excessive Authentication Attempts | The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks. | CWE-799 | 309 |
| 80 | 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. | | 308 |
| 81 | CWE-384 | Session Fixiation | Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions. | | 302 |
| 82 | CWE-23 | Relative Path Traversal | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. | CWE-22 | 292 |
| 83 | CWE-259 | Use of Hard-coded Password | The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. | CWE-255 | 289 |
| 84 | CWE-613 | Session Expiration | According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." | | 281 |
| 85 | CWE-444 | HTTP Request Smuggling | The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. | | 273 |
| 86 | CWE-327 | Risky Cryptographic Algorithm | The product uses a broken or risky cryptographic algorithm or protocol. | CWE-310 | 270 |
| 87 | CWE-754 | Improper Check for Unusual Conditions | The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. | | 268 |
| 88 | CWE-1021 | Improper Restriction of Rendered UI Layers | The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with. | | 266 |
| 89 | CWE-367 | Time-of-check Time-of-use | The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state. | CWE-362 | 264 |
| 90 | CWE-789 | Uncontrolled Memory Allocation | The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. | CWE-400 | 261 |
| 91 | CWE-192 | Integer Coercion Error | Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types. | CWE-189 | 253 |
| 92 | CWE-704 | Incorrect Type Conversion | The product does not correctly convert an object, resource, or structure from one type to a different type. | | 247 |
| 93 | CWE-833 | Deadlock | The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. | CWE-404 | 240 |
| 94 | CWE-321 | Use of Hard-coded Cryptographic Key
| The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. | CWE-320 | 239 |
| 95 | CWE-640 | Weak Password Recovery | The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak. | | 226 |
| 96 | CWE-755 | Handling of Exceptional Conditions | The product does not handle or incorrectly handles an exceptional condition. | | 225 |
| 97 | CWE-99 | Improper Control of Resource Identifiers | The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. | | 219 |
| 98 | CWE-17 | Code | | | 213 |
| 99 | CWE-191 | Integer Underflow | The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result. | CWE-189 | 212 |
| 100 | CWE-265 | Sandbox Issue | | CWE-264 | 208 |
| 101 | CWE-330 | Insufficiently Random Values | The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers. | CWE-310 | 207 |
| 102 | CWE-428 | Unquoted Search Path | The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. | CWE-426 | 202 |
| 103 | CWE-203 | Information Exposure Through Discrepancy | The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not. | CWE-200 | 201 |
| 104 | CWE-552 | Files or Directories Accessible | The product makes files or directories accessible to unauthorized actors, even though they should not be. | CWE-425 | 201 |
| 105 | CWE-911 | Improper Update of Reference Count | The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. | CWE-664 | 197 |
| 106 | CWE-288 | Authentication Bypass Using Alternate Channel | A product requires authentication, but the product has an alternate path or channel that does not require authentication. | CWE-287 | 194 |
| 107 | CWE-256 | Unprotected Storage of Credentials | Storing a password in plaintext may result in a system compromise. | CWE-255 | 193 |
| 108 | CWE-451 | Clickjacking | The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks. | | 190 |
| 109 | CWE-942 | Permissive Cross-domain Policy with Untrusted Domains | The product uses a cross-domain policy file that includes domains that should not be trusted. | CWE-346 | 187 |
| 110 | CWE-1321 | Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') | The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. | CWE-94 | 186 |
| 111 | CWE-1236 | CSV Injection | The product saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as a command when the file is opened by a spreadsheet product. | CWE-74 | 183 |
| 112 | CWE-668 | Exposure of Resource | The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. | CWE-200 | 167 |
| 113 | CWE-346 | Origin Validation Error | The product does not properly verify that the source of data or communication is valid. | CWE-345 | 165 |
| 114 | CWE-358 | Security Check for Standard | The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique. | | 164 |
| 115 | CWE-126 | Buffer Over-read | The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer. | CWE-119 | 162 |
| 116 | CWE-377 | Insecure Temporary File | Creating and using insecure temporary files can leave application and system data vulnerable to attack. | | 160 |
| 117 | CWE-266 | Incorrect Privilege Assignment | A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor. | | 159 |
| 118 | CWE-88 | Argument Injection | The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string. | CWE-74 | 157 |
| 119 | CWE-1333 | Inefficient Regular Expression Complexity | The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. | CWE-400 | 154 |
| 120 | CWE-320 | Key Management Error | | | 146 |
| 121 | CWE-908 | Uninitialized Resource | The product uses or accesses a resource that has not been initialized. | | 143 |
| 122 | CWE-185 | Incorrect Regular Expression | The product specifies a regular expression in a way that causes data to be improperly matched or compared. | CWE-697 | 141 |
| 123 | CWE-300 | Channel Accessible by Non-Endpoint | The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. | | 141 |
| 124 | CWE-250 | Execution with Unnecessary Privileges | The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses. | | 140 |
| 125 | CWE-208 | Observable Timing Discrepancy | Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not. | CWE-203 | 133 |
| 126 | CWE-521 | Weak Password Requirements | The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. | | 126 |
| 127 | CWE-252 | Unchecked Return Value | The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions. | CWE-253 | 124 |
| 128 | CWE-193 | Off-by-One | A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value. | CWE-189 | 121 |
| 129 | CWE-294 | Authentication Bypass by Capture-replay | A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). | CWE-287 | 119 |
| 130 | CWE-494 | Download of Code Without Integrity Check | The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code. | | 113 |
| 131 | CWE-841 | Enforcement of Behavioral Workflow | The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence. | CWE-840 | 108 |
| 132 | CWE-674 | Uncontrolled Recursion | The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack. | CWE-404 | 107 |
| 133 | CWE-281 | Preservation of Permissions | The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended. | CWE-266 | 103 |
| 134 | CWE-93 | CRLF Injection | The product 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. | CWE-74 | 101 |
| 135 | CWE-98 | Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') | The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. | | 99 |
| 136 | CWE-354 | Improper Validation of Integrity Check Value | The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission. | CWE-345 | 96 |
| 137 | CWE-697 | Incorrect Comparison | The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses. | | 94 |
| 138 | CWE-772 | Missing Release of Resource | The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. | CWE-400 | 90 |
| 139 | CWE-331 | Insufficient Entropy | The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others. | CWE-330 | 88 |
| 140 | CWE-670 | Incorrect Control Flow | The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated. | | 88 |
| 141 | CWE-610 | Externally Controlled Reference | The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere. | | 86 |
| 142 | CWE-91 | XML Injection | The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system. | CWE-74 | 83 |
| 143 | CWE-113 | HTTP Response Splitting | The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers. | CWE-93 | 81 |
| 144 | CWE-204 | Observable Response Discrepancy | The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere. | CWE-203 | 79 |
| 145 | CWE-116 | Escaping of Output | The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved. | CWE-74 | 78 |
| 146 | CWE-117 | Improper Output Neutralization for Logs | The product does not neutralize or incorrectly neutralizes output that is written to logs. | CWE-116 | 74 |
| 147 | CWE-922 | Insecure Storage of Sensitive Information | The product stores sensitive information without properly limiting read or write access by unauthorized actors. | CWE-200 | 72 |
| 148 | CWE-338 | Cryptographically Weak PRNG | The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong. | CWE-331 | 70 |
| 149 | CWE-184 | Incomplete Blacklist | The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete, leading to resultant weaknesses. | CWE-183 | 69 |
| 150 | CWE-24 | Path Traversal: '../filedir' | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory. | CWE-23 | 69 |
| 151 | CWE-749 | Exposed Dangerous Routine | The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted. | | 69 |
| 152 | CWE-201 | Insertion of Sensitive Information Into Sent Data | The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. | CWE-200 | 68 |
| 153 | CWE-280 | Improper Handling of Insufficient Permissions or Privileges | The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state. | CWE-266 | 68 |
| 154 | CWE-497 | Exposure of Sensitive System Information to an Unauthorized Control Sphere | The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. | | 66 |
| 155 | CWE-614 | Sensitive Cookie Without Secure Attribute | The Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the user agent to send those cookies in plaintext over an HTTP session. | CWE-1004 | 66 |
| 156 | CWE-916 | Password Hash With Insufficient Computational Effort | The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive. | CWE-326 | 66 |
| 157 | CWE-305 | Authentication Bypass by Primary Weakness | The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. | CWE-287 | 65 |
| 158 | CWE-388 | 7PK Error | | | 64 |
| 159 | CWE-35 | Path Traversal: '.../...//' | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '.../...//' (doubled triple dot slash) sequences that can resolve to a location that is outside of that directory. | CWE-23 | 63 |
| 160 | CWE-90 | LDAP Injection | The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component. | CWE-74 | 63 |
| 161 | CWE-1392 | Use of Default Credentials | The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality. | | 62 |
| 162 | CWE-297 | Certificate with Host Mismatch | The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host. | CWE-295 | 61 |
| 163 | CWE-822 | Untrusted Pointer Dereference | The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer. | | 61 |
| 164 | CWE-840 | Business Logic Errors | | | 59 |
| 165 | CWE-95 | Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval"). | CWE-20 | 56 |
| 166 | CWE-703 | Improper Check or Handling of Exceptional Conditions | The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product. | | 55 |
| 167 | CWE-1018 | Manage User Sessions | | | 54 |
| 168 | CWE-682 | Incorrect Calculation | The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management. | | 53 |
| 169 | CWE-248 | Uncaught Exception | An exception is thrown from a function, but it is not caught. | | 52 |
| 170 | CWE-29 | Path Traversal: '\..\filename' | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory. | CWE-23 | 52 |
| 171 | CWE-359 | Exposure of Private Personal Information to an Unauthorized Actor | The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. | | 50 |
| 172 | CWE-379 | Creation of Temporary File in Directory with Insecure Permissions | The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file. | CWE-377 | 48 |
| 173 | CWE-425 | Direct Request | The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files. | | 48 |
| 174 | CWE-459 | Incomplete Cleanup | The product does not properly "clean up" and remove temporary or supporting resources after they have been used. | | 48 |
| 175 | CWE-538 | File and Directory Information Exposure | The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information. | CWE-200 | 48 |
| 176 | CWE-829 | Inclusion of Functionality from Untrusted Control Sphere | The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. | | 48 |
| 177 | CWE-36 | Absolute Path Traversal | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as "/abs/path" that can resolve to a location that is outside of that directory. | CWE-22 | 47 |
| 178 | CWE-170 | Improper Null Termination | The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator. | CWE-119 | 46 |
| 179 | CWE-834 | Excessive Iteration | The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed. | CWE-404 | 45 |
| 180 | CWE-1188 | Insecure Default Initialization of Resource | The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure. | | 42 |
| 181 | CWE-274 | Improper Handling of Insufficient Privileges | The product does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses. | CWE-266 | 40 |
| 182 | CWE-667 | Improper Locking | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. | | 39 |
| 183 | CWE-707 | Improper Neutralization | The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component. | CWE-20 | 39 |
| 184 | CWE-1004 | Cookie Without 'HttpOnly' Flag | The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag. | CWE-732 | 38 |
| 185 | CWE-1284 | Improper Validation of Specified Quantity in Input | The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties. | CWE-20 | 38 |
| 186 | CWE-1336 | Improper Neutralization of Special Elements Used in a Template Engine | The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine. | CWE-791 | 38 |
| 187 | CWE-457 | Use of Uninitialized Variable | The code uses a variable that has not been initialized, leading to unpredictable or unintended results. | CWE-453 | 37 |
| 188 | CWE-489 | Active Debug Code | The product is deployed to unauthorized actors with debugging code still enabled or active, which can create unintended entry points or expose sensitive information. | | 37 |
| 189 | CWE-1287 | Improper Validation of Specified Type of Input | The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type. | CWE-20 | 35 |
| 190 | CWE-131 | Incorrect Calculation of Buffer Size | The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow. | CWE-120 | 35 |
| 191 | CWE-277 | Insecure Inherited Permissions | A product defines a set of insecure permissions that are inherited by objects that are created by the program. | CWE-266 | 35 |
| 192 | CWE-332 | Insufficient Entropy in PRNG | The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat. | CWE-331 | 35 |
| 193 | CWE-776 | XML Entity Expansion | The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities. | | 35 |
| 194 | CWE-823 | Use of Out-of-range Pointer Offset | The product performs pointer arithmetic on a valid pointer, but it uses an offset that can point outside of the intended range of valid memory locations for the resulting pointer. | | 35 |
| 195 | CWE-407 | Inefficient Algorithmic Complexity | An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. | CWE-404 | 34 |
| 196 | CWE-172 | Encoding Error | The product does not properly encode or decode the data, resulting in unexpected values. | | 33 |
| 197 | CWE-123 | Write-what-where Condition | Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow. | CWE-119 | 32 |
| 198 | CWE-328 | Use of Weak Hash | The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack). | CWE-327 | 32 |
| 199 | CWE-757 | Algorithm Downgrade | A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties. | | 32 |
| 200 | CWE-18 | Source Code | | CWE-17 | 31 |
| 201 | CWE-602 | Client-Side Enforcement of Server-Side Security | The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server. | | 31 |
| 202 | CWE-913 | Dynamically-Managed Code Resources | The product 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. | | 31 |
| 203 | CWE-303 | Incorrect Implementation of Authentication Algorithm | The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect. | | 30 |
| 204 | CWE-417 | Path Error | | | 30 |
| 205 | CWE-669 | Incorrect Resource Transfer | 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. | | 30 |
| 206 | CWE-672 | Operation on a Resource after Expiration | The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. | | 30 |
| 207 | CWE-15 | External Control of System or Configuration Setting | One or more system settings or configuration elements can be externally controlled by a user. | | 29 |
| 208 | CWE-313 | Cleartext Storage in a File or on Disk | The product stores sensitive information in cleartext in a file, or on disk. | CWE-312 | 29 |
| 209 | CWE-909 | Missing Initialization of Resource | The product does not initialize a critical resource. | CWE-908 | 29 |
| 210 | CWE-927 | Use of Implicit Intent for Sensitive Communication | The Android application uses an implicit intent for transmitting sensitive data to other applications. | | 29 |
| 211 | CWE-620 | Unverified Password Change | When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication. | CWE-640 | 28 |
| 212 | CWE-664 | Improper Control of Resource Through Lifetime | The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release. | | 28 |
| 213 | CWE-1220 | Insufficient Granularity of Access Control | The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. | CWE-284 | 27 |
| 214 | CWE-534 | Information Exposure Through Debug Log File | This entry has been deprecated because its abstraction was too low-level. See CWE-532. | CWE-532 | 27 |
| 215 | CWE-681 | Incorrect Conversion between Numeric Types | When converting from one data type to another, such as long to integer, data can be omitted or translated in a way that produces unexpected values. If the resulting values are used in a sensitive context, then dangerous behaviors may occur. | CWE-704 | 27 |
| 216 | CWE-130 | Improper Handling of Length Parameter Inconsistency | The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data. | CWE-119 | 26 |
| 217 | CWE-273 | Improper Check for Dropped Privileges | The product attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded. | CWE-266 | 26 |
| 218 | CWE-548 | Exposure of Information Through Directory Listing | A directory listing is inappropriately exposed, yielding potentially sensitive information to attackers. | CWE-552 | 26 |
| 219 | CWE-648 | Incorrect Use of Privileged APIs | The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly. | | 26 |
| 220 | CWE-118 | Range Error | The product does not restrict or incorrectly restricts operations within the boundaries of a resource that is accessed using an index or pointer, such as memory or files. | | 25 |
| 221 | CWE-197 | Numeric Truncation Error | Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion. | CWE-189 | 25 |
| 222 | CWE-436 | Interpretation Conflict | Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state. | | 25 |
| 223 | CWE-926 | Improper Export of Android Application Components | The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains. | | 25 |
| 224 | CWE-25 | Path Traversal: '/../filedir' | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/../" sequences that can resolve to a location that is outside of that directory. | CWE-23 | 24 |
| 225 | CWE-257 | Storing Passwords in a Recoverable Format | The storage of passwords in a recoverable format makes them subject to password reuse attacks by malicious users. In fact, it should be noted that recoverable encrypted passwords provide no significant benefit over plaintext passwords since they are subject not only to reuse by malicious attackers but also by malicious insiders. If a system administrator can recover a password directly, or use a brute force search on the available information, the administrator can use the password on other accounts. | CWE-255 | 24 |
| 226 | CWE-261 | Weak Encoding for Password | Obscuring a password with a trivial encoding does not protect the password. | CWE-257 | 24 |
| 227 | CWE-598 | Use of GET Request Method With Sensitive Query Strings | The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. | | 24 |
| 228 | CWE-763 | Release of Reference | The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly. | CWE-404 | 24 |
| 229 | CWE-92 | Improper Sanitization of Custom Special Characters (deprecated) | This entry has been deprecated. It originally came from PLOVER, which sometimes defined "other" and "miscellaneous" categories in order to satisfy exhaustiveness requirements for taxonomies. Within the context of CWE, the use of a more abstract entry is preferred in mapping situations. CWE-75 is a more appropriate mapping. | CWE-74 | 24 |
| 230 | CWE-769 | Uncontrolled File Descriptor Consumption | This entry has been deprecated because it was a duplicate of CWE-774. All content has been transferred to CWE-774. | CWE-400 | 23 |
| 231 | CWE-915 | Dynamically-Determined Object Attributes | The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified. | CWE-913 | 23 |
| 232 | CWE-1390 | Weak Authentication | The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct. | | 22 |
| 233 | CWE-350 | Reliance on Reverse DNS Resolution | The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname. | | 22 |
| 234 | CWE-470 | Use of Externally-Controlled Input to Select Classes or Code | The product 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. | | 22 |
| 235 | CWE-472 | External Control of Assumed-Immutable Web Parameter | The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields. | | 22 |
| 236 | CWE-680 | Integer Overflow to Buffer Overflow | The product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow. | CWE-190 | 22 |
| 237 | CWE-799 | Improper Control of Interaction Frequency | The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests. | CWE-400 | 22 |
| 238 | CWE-923 | Improper Restriction of Communication Channel to Intended Endpoints | The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint. | | 22 |
| 239 | CWE-924 | Improper Enforcement of Message Integrity | The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission. | CWE-354 | 22 |
| 240 | CWE-1286 | Improper Validation of Syntactic Correctness of Input | The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax. | CWE-20 | 21 |
| 241 | CWE-644 | Improper Neutralization of HTTP Headers for Scripting Syntax | The product does not neutralize or incorrectly neutralizes web scripting syntax in HTTP headers that can be used by web browser components that can process raw headers, such as Flash. | | 21 |
| 242 | CWE-706 | Incorrectly-Resolved Name | The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. | | 21 |
| 243 | CWE-917 | Improper Neutralization of Special Elements used in an Expression Language Statement | The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed. | CWE-20 | 20 |
| 244 | CWE-1187 | Use of Uninitialized Resource (deprecated) | This entry has been deprecated because it was a duplicate of CWE-908. All content has been transferred to CWE-908. | CWE-908 | 19 |
| 245 | CWE-323 | Reusing a Nonce | Nonces should be used for the present occasion and only once. | | 19 |
| 246 | CWE-788 | Access of Memory Location After End of Buffer | The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer. | CWE-120 | 19 |
| 247 | CWE-267 | Privilege Defined With Unsafe Actions | A particular privilege, role, capability, or right can be used to perform unsafe actions that were not intended, even when it is assigned to the correct entity. | CWE-266 | 18 |
| 248 | CWE-378 | Creation of Temporary File With Insecure Permissions | Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack. | CWE-377 | 18 |
| 249 | CWE-690 | Unchecked Return Value to NULL Pointer Dereference | The product does not check for an error after calling a function that can return with a NULL pointer if the function fails, which leads to a resultant NULL pointer dereference. | CWE-395 | 18 |
| 250 | CWE-759 | One-Way Hash without Salt | The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product does not also use a salt as part of the input. | CWE-325 | 18 |
| 251 | CWE-316 | Cleartext Storage of Sensitive Information in Memory | The product stores sensitive information in cleartext in memory. | CWE-312 | 17 |
| 252 | CWE-361 | 7PK Time and State | | | 17 |
| 253 | CWE-41 | Improper Resolution of Path Equivalence | The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object. | | 17 |
| 254 | CWE-441 | Unintended Intermediary | The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor. | | 17 |
| 255 | CWE-456 | Missing Initialization of a Variable | The product does not initialize critical variables, which causes the execution environment to use unexpected values. | CWE-453 | 17 |
| 256 | CWE-591 | Sensitive Data Storage in Improperly Locked Memory | 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. | CWE-200 | 17 |
| 257 | CWE-778 | Insufficient Logging | When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it. | | 17 |
| 258 | CWE-440 | Expected Behavior Violation | A feature, API, or function does not perform according to its specification. | CWE-436 | 16 |
| 259 | CWE-565 | Cookies without Validation | The product 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. | CWE-20 | 16 |
| 260 | CWE-1391 | Use of Weak Credentials | The product uses weak credentials (such as a default key or hard-coded password) that can be calculated, derived, reused, or guessed by an attacker. | | 15 |
| 261 | CWE-1393 | Use of Default Password | The product uses default passwords for potentially critical functionality. | | 15 |
| 262 | CWE-282 | Improper Ownership Management | The product assigns the wrong ownership, or does not properly verify the ownership, of an object or resource. | CWE-284 | 15 |
| 263 | CWE-302 | Authentication Bypass by Assumed-Immutable Data | The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker. | | 15 |
| 264 | CWE-304 | Missing Critical Step in Authentication | The product implements an authentication technique, but it skips a step that weakens the technique. | | 15 |
| 265 | CWE-807 | Reliance on Untrusted Inputs in a Security Decision | The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism. | CWE-20 | 15 |
| 266 | CWE-940 | Improper Verification of Source of a Communication Channel | The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin. | | 15 |
| 267 | CWE-1288 | Improper Validation of Consistency within Input | The product receives a complex input with multiple elements or fields that must be consistent with each other, but it does not validate or incorrectly validates that the input is actually consistent. | CWE-20 | 14 |
| 268 | CWE-322 | Key Exchange without Entity Authentication | The product performs a key exchange with an actor without verifying the identity of that actor. | CWE-320 | 14 |
| 269 | CWE-661 | PHP Weakness | | | 14 |
| 270 | CWE-150 | Improper Neutralization of Escape, Meta, or Control Sequences | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component. | CWE-20 | 13 |
| 271 | CWE-212 | Improper Removal of Sensitive Information Before Storage or Transfer | The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors. | CWE-200 | 13 |
| 272 | CWE-213 | Exposure of Sensitive Information Due to Incompatible Policies | The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product's administrator, users, or others whose information is being processed. | CWE-200 | 13 |
| 273 | CWE-241 | Improper Handling of Unexpected Data Type | The product does not handle or incorrectly handles when a particular element is not the expected type, e.g. it expects a digit (0-9) but is provided with a letter (A-Z). | CWE-229 | 13 |
| 274 | CWE-270 | Privilege Context Switching Error | The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control. | CWE-266 | 13 |
| 275 | CWE-286 | Incorrect User Management | The product does not properly manage a user within its environment. | | 13 |
| 276 | CWE-385 | Covert Timing Channel | Covert timing channels convey information by modulating some aspect of system behavior over time, so that the program receiving the information can observe system behavior and infer protected information. | | 13 |
| 277 | CWE-549 | Missing Password Field Masking | The product does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords. | CWE-200 | 13 |
| 278 | CWE-653 | Improper Isolation or Compartmentalization | The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions. | | 13 |
| 279 | CWE-1230 | Exposure of Sensitive Information Through Metadata | The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information. | CWE-200 | 12 |
| 280 | CWE-1385 | Missing Origin Validation in WebSockets | The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid. | CWE-346 | 12 |
| 281 | CWE-27 | Path Traversal: 'dir/../../filename' | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize multiple internal "../" sequences that can resolve to a location that is outside of that directory. | CWE-23 | 12 |
| 282 | CWE-325 | Missing Cryptographic Step | The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm. | | 12 |
| 283 | CWE-349 | Acceptance of Extraneous Untrusted Data With Trusted Data | The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted. | | 12 |
| 284 | CWE-540 | Inclusion of Sensitive Information in Source Code | Source code on a web server or repository often contains sensitive information and should generally not be accessible to users. | CWE-200 | 12 |
| 285 | CWE-114 | Process Control | Executing commands or loading libraries from an untrusted source or in an untrusted environment can cause an application to execute malicious commands (and payloads) on behalf of an attacker. | | 11 |
| 286 | CWE-115 | Misinterpretation of Input | The product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion. | CWE-20 | 11 |
| 287 | CWE-124 | Buffer Underwrite | The product writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer. | CWE-119 | 11 |
| 288 | CWE-1285 | Improper Validation of Specified Index, Position, or Offset in Input | The product receives input that is expected to specify an index, position, or offset into an indexable resource such as a buffer or file, but it does not validate or incorrectly validates that the specified index/position/offset has the required properties. | | 11 |
| 289 | CWE-199 | Information Management Error | | CWE-200 | 11 |
| 290 | CWE-205 | Observable Behavioral Discrepancy | The product's behaviors indicate important differences that may be observed by unauthorized actors in a way that reveals (1) its internal state or decision process, or (2) differences from other products with equivalent functionality. | CWE-203 | 11 |
| 291 | CWE-226 | Sensitive Information in Resource Not Removed Before Reuse | The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or "zeroize" the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities. | CWE-200 | 11 |
| 292 | CWE-233 | Improper Handling of Parameters | The product does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined. | CWE-229 | 11 |
| 293 | CWE-272 | Least Privilege Violation | The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed. | CWE-266 | 11 |
| 294 | CWE-353 | Missing Support for Integrity Check | The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum. | | 11 |
| 295 | CWE-501 | Trust Boundary Violation | The product mixes trusted and untrusted data in the same data structure or structured message. | | 11 |
| 296 | CWE-506 | Embedded Malicious Code | The product contains code that appears to be malicious in nature. | | 11 |
| 297 | CWE-524 | Use of Cache Containing Sensitive Information | The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. | | 11 |
| 298 | CWE-691 | Insufficient Control Flow Management | The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways. | | 11 |
| 299 | CWE-75 | Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) | The product does not adequately filter user-controlled input for special elements with control implications. | CWE-707 | 11 |
| 300 | CWE-1022 | Use of Web Link to Untrusted Target with window.opener Access | The web application produces links to untrusted external sites outside of its sphere of control, but it does not properly prevent the external site from modifying security-critical properties of the window.opener object, such as the location property. | CWE-266 | 10 |
| 301 | CWE-1104 | Use of Unmaintained Third Party Components | 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. | | 10 |
| 302 | CWE-178 | Improper Handling of Case Sensitivity | The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. | CWE-697 | 10 |
| 303 | CWE-335 | Incorrect Usage of Seeds in PRNG | The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds. | CWE-331 | 10 |
| 304 | CWE-405 | Asymmetric Resource Consumption | The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric." | CWE-400 | 10 |
| 305 | CWE-424 | Improper Protection of Alternate Path | The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources. | | 10 |
| 306 | CWE-471 | Modification of Assumed-Immutable Data | The product does not properly protect an assumed-immutable element from being modified by an attacker. | | 10 |
| 307 | CWE-525 | Use of Web Browser Cache Containing Sensitive Information | The web application does not use an appropriate caching policy that specifies the extent to which each web page and associated form fields should be cached. | CWE-524 | 10 |
| 308 | CWE-805 | Buffer Access with Incorrect Length Value | The product uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer. | CWE-120 | 10 |
| 309 | CWE-943 | Improper Neutralization of Special Elements in Data Query Logic | The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query. | CWE-20 | 10 |
| 310 | CWE-96 | Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template. | CWE-20 | 10 |
| 311 | CWE-158 | Improper Neutralization of Null Byte or NUL Character | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component. | CWE-20 | 9 |
| 312 | CWE-228 | Improper Handling of Syntactically Invalid Structure | The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification. | CWE-20 | 9 |
| 313 | CWE-258 | Empty Password in Configuration File | Using an empty string as a password is insecure. | CWE-259 | 9 |
| 314 | CWE-279 | Incorrect Execution-Assigned Permissions | While it is executing, the product sets the permissions of an object in a way that violates the intended permissions that have been specified by the user. | CWE-266 | 9 |
| 315 | CWE-324 | Use of a Key Past its Expiration Date | The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attacks against that key. | CWE-320 | 9 |
| 316 | CWE-348 | Use of Less Trusted Source | The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack. | | 9 |
| 317 | CWE-420 | Unprotected Alternate Channel | The product protects a primary channel, but it does not use the same level of protection for an alternate channel. | CWE-419 | 9 |
| 318 | CWE-696 | Incorrect Behavior Order | The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways which may produce resultant weaknesses. | | 9 |
| 319 | CWE-1263 | Improper Physical Access Control | The product is designed with access restricted to certain information, but it does not sufficiently protect against an unauthorized actor with physical access to these areas. | CWE-284 | 8 |
| 320 | CWE-1275 | Sensitive Cookie with Improper SameSite Attribute | The SameSite attribute for sensitive cookies is not set, or an insecure value is used. | CWE-346 | 8 |
| 321 | CWE-1295 | Debug Messages Revealing Unnecessary Information | The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages. | CWE-200 | 8 |
| 322 | CWE-1386 | Insecure Operation on Windows Junction / Mount Point | The product opens a file or directory, but it does not properly prevent the name from being associated with a junction or mount point to a destination that is outside of the intended control sphere. | | 8 |
| 323 | CWE-14 | Compiler Removal of Code to Clear Buffers | Sensitive memory is cleared according to the source code, but compiler optimizations leave the memory untouched when it is not read from again, aka "dead store removal." | | 8 |
| 324 | CWE-140 | Improper Neutralization of Delimiters | The product does not neutralize or incorrectly neutralizes delimiters. | CWE-20 | 8 |
| 325 | CWE-183 | Permissive List of Allowed Inputs | The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses. | CWE-20 | 8 |
| 326 | CWE-357 | Insufficient UI Warning of Dangerous Operations | The user interface provides a warning to a user regarding dangerous or sensitive operations, but the warning is not noticeable enough to warrant attention. | CWE-356 | 8 |
| 327 | CWE-409 | Highly Compressed Data | The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output. | CWE-404 | 8 |
| 328 | CWE-475 | Undefined Behavior for Input to API | The behavior of this function is undefined unless its control parameter is set to a specific value. | | 8 |
| 329 | CWE-523 | Unprotected Transport of Credentials | Login pages do not use adequate measures to protect the user name and password while they are in transit from the client to the server. | CWE-522 | 8 |
| 330 | CWE-636 | Not Failing Securely | When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions. | | 8 |
| 331 | CWE-642 | External Control of Critical State Data | The product stores security-critical state information about its users, or the product itself, in a location that is accessible to unauthorized actors. | | 8 |
| 332 | CWE-684 | Incorrect Provision of Specified Functionality | The code does not function according to its published specifications, potentially leading to incorrect usage. | | 8 |
| 333 | CWE-821 | Incorrect Synchronization | The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource. | | 8 |
| 334 | CWE-825 | Expired Pointer Dereference | The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid. | | 8 |
| 335 | CWE-925 | Improper Verification of Intent by Broadcast Receiver | The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source. | | 8 |
| 336 | CWE-1327 | Binding to an Unrestricted IP Address | The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely. | CWE-284 | 7 |
| 337 | CWE-1394 | Use of Default Cryptographic Key | The product uses a default cryptographic key for potentially critical functionality. | | 7 |
| 338 | CWE-202 | Exposure of Sensitive Information Through Data Queries | When trying to keep information confidential, an attacker can often infer some of the information by using statistics. | CWE-200 | 7 |
| 339 | CWE-260 | Password in Configuration File | The product stores a password in a configuration file that might be accessible to actors who do not know the password. | CWE-255 | 7 |
| 340 | CWE-289 | Authentication Bypass by Alternate Name | The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor. | CWE-287 | 7 |
| 341 | CWE-334 | Small Space of Random Values | The number of possible random values is smaller than needed by the product, making it more susceptible to brute force attacks. | CWE-331 | 7 |
| 342 | CWE-395 | Use of NullPointerException Catch to Detect NULL Pointer Dereference | Catching NullPointerException should not be used as an alternative to programmatic checks to prevent dereferencing a null pointer. | | 7 |
| 343 | CWE-406 | Insufficient Control of Network Message Volume | The product does not sufficiently monitor or control transmitted network traffic volume, so that an actor can cause the product to transmit more traffic than should be allowed for that actor. | CWE-400 | 7 |
| 344 | CWE-453 | Insecure Default Variable Initialization | The product, by default, initializes an internal variable with an insecure or less secure value than is possible. | | 7 |
| 345 | CWE-530 | Exposure of Backup File to an Unauthorized Control Sphere | A backup file is stored in a directory or archive that is made accessible to unauthorized actors. | CWE-285 | 7 |
| 346 | CWE-547 | Use of Hard-coded, Security-relevant Constants | The product uses hard-coded constants instead of symbolic names for security-critical values, which increases the likelihood of mistakes during code maintenance or security policy change. | | 7 |
| 347 | CWE-603 | Use of Client-Side Authentication | 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. | CWE-602 | 7 |
| 348 | CWE-641 | Improper Restriction of Names for Files and Other Resources | The product constructs the name of a file or other resource using input from an upstream component, but it does not restrict or incorrectly restricts the resulting name. | | 7 |
| 349 | CWE-657 | Violation of Secure Design Principles | The product violates well-established principles for secure design. | | 7 |
| 350 | CWE-698 | Execution After Redirect | The web application sends a redirect to another location, but instead of exiting, it executes additional code. | CWE-705 | 7 |
| 351 | CWE-836 | Use of Password Hash Instead of Password for Authentication | The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store. | | 7 |
| 352 | CWE-1204 | Generation of Weak Initialization Vector | The product uses a cryptographic primitive that uses an Initialization Vector (IV), but the product does not generate IVs that are sufficiently unpredictable or unique according to the expected cryptographic requirements for that primitive. | CWE-310 | 6 |
| 353 | CWE-1242 | Inclusion of Undocumented Features or Chicken Bits | The device includes chicken bits or undocumented features that can create entry points for unauthorized actors. | CWE-912 | 6 |
| 354 | CWE-1299 | Missing Protection Mechanism for Alternate Hardware Interface | The lack of protections on alternate paths to access control-protected assets (such as unprotected shadow registers and other external facing unguarded interfaces) allows an attacker to bypass existing protections to the asset that are only performed against the primary path. | | 6 |
| 355 | CWE-138 | Improper Neutralization of Special Elements | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as control elements or syntactic markers when they are sent to a downstream component. | CWE-20 | 6 |
| 356 | CWE-146 | Improper Neutralization of Expression/Command Delimiters | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as expression or command delimiters when they are sent to a downstream component. | CWE-140 | 6 |
| 357 | CWE-155 | Improper Neutralization of Wildcards or Matching Symbols | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as wildcards or matching symbols when they are sent to a downstream component. | CWE-20 | 6 |
| 358 | CWE-195 | Signed to Unsigned Conversion Error | The product uses a signed primitive and performs a cast to an unsigned primitive, which can produce an unexpected value if the value of the signed primitive can not be represented using an unsigned primitive. | CWE-194 | 6 |
| 359 | CWE-214 | Invocation of Process Using Visible Sensitive Information | A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system. | | 6 |
| 360 | CWE-215 | Insertion of Sensitive Information Into Debugging Code | The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production. | CWE-200 | 6 |
| 361 | CWE-271 | Privilege Dropping / Lowering Errors | The product does not drop privileges before passing control of a resource to an actor that does not have those privileges. | CWE-270 | 6 |
| 362 | CWE-308 | Use of Single-factor Authentication | The use of single-factor authentication can lead to unnecessary risk of compromise when compared with the benefits of a dual-factor authentication scheme. | CWE-287 | 6 |
| 363 | CWE-341 | Predictable from Observable State | A number or object is predictable based on observations that the attacker can make about the state of the system or network, such as time, process ID, etc. | CWE-200 | 6 |
| 364 | CWE-366 | Race Condition within a Thread | If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined. | CWE-362 | 6 |
| 365 | CWE-391 | Unchecked Error Condition | [PLANNED FOR DEPRECATION. SEE MAINTENANCE NOTES AND CONSIDER CWE-252, CWE-248, OR CWE-1069.] Ignoring exceptions and other error conditions may allow an attacker to induce unexpected behavior unnoticed. | | 6 |
| 366 | CWE-410 | Insufficient Resource Pool | The product's resource pool is not large enough to handle peak demand, which allows an attacker to prevent others from accessing the resource by using a (relatively) large number of requests for resources. | CWE-404 | 6 |
| 367 | CWE-443 | HTTP Response Splitting (deprecated) | This weakness can be found at CWE-113. | CWE-436 | 6 |
| 368 | CWE-460 | Improper Cleanup on Thrown Exception | The product does not clean up its state or incorrectly cleans up its state when an exception is thrown, leading to unexpected state or control flow. | CWE-459 | 6 |
| 369 | CWE-477 | Use of Obsolete Function | The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained. | CWE-474 | 6 |
| 370 | CWE-488 | Exposure of Data Element to Wrong Session | The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session. | | 6 |
| 371 | CWE-650 | Trusting HTTP Permission Methods on the Server Side | The server contains a protection mechanism that assumes that any URI that is accessed using HTTP GET will not cause a state change to the associated resource. This might allow attackers to bypass intended access restrictions and conduct resource modification and deletion attacks, since some applications allow GET to modify state. | | 6 |
| 372 | CWE-694 | Use of Multiple Resources with Duplicate Identifier | The product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required. | | 6 |
| 373 | CWE-76 | Improper Neutralization of Equivalent Special Elements | The product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements. | CWE-707 | 6 |
| 374 | CWE-804 | Guessable CAPTCHA | The product uses a CAPTCHA challenge, but the challenge can be guessed or automatically recognized by a non-human actor. | CWE-287 | 6 |
| 375 | CWE-837 | Improper Enforcement of a Single, Unique Action | The product requires that an actor should only be able to perform an action once, or to have only one unique action, but the product does not enforce or improperly enforces this restriction. | | 6 |
| 376 | CWE-939 | Improper Authorization in Handler for Custom URL Scheme | The product uses a handler for a custom URL scheme, but it does not properly restrict which actors can invoke the handler using the scheme. | CWE-285 | 6 |
| 377 | CWE-1191 | On-Chip Debug and Test Interface With Improper Access Control | The chip does not implement or does not correctly perform access control to check whether users are authorized to access internal registers and test modes through the physical debug/test interface. | | 5 |
| 378 | CWE-128 | Wrap-around Error | Wrap around errors occur whenever a value is incremented past the maximum value for its type and therefore "wraps around" to a very small, negative, or undefined value. | CWE-119 | 5 |
| 379 | CWE-1320 | Improper Protection for Out of Bounds Signal Level Alerts | Untrusted agents can disable alerts about signal conditions exceeding limits or the response mechanism that handles such alerts. | | 5 |
| 380 | CWE-1326 | Missing Immutable Root of Trust in Hardware | A missing immutable root of trust in the hardware results in the ability to bypass secure boot or execute untrusted or adversarial boot code. | | 5 |
| 381 | CWE-176 | Improper Handling of Unicode Encoding | The product does not properly handle when an input contains Unicode encoding. | CWE-172 | 5 |
| 382 | CWE-187 | Partial String Comparison | The product performs a comparison that only examines a portion of a factor before determining whether there is a match, such as a substring, leading to resultant weaknesses. | CWE-697 | 5 |
| 383 | CWE-230 | Improper Handling of Missing Values | The product does not handle or incorrectly handles when a parameter, field, or argument name is specified, but the associated value is missing, i.e. it is empty, blank, or null. | CWE-229 | 5 |
| 384 | CWE-249 | Path Manipulation (deprecated) | This entry has been deprecated because of name confusion and an accidental combination of multiple weaknesses. Most of its content has been transferred to CWE-785. | | 5 |
| 385 | CWE-253 | Incorrect Check of Function Return Value | The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions. | | 5 |
| 386 | CWE-268 | Privilege Chaining | Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination. | CWE-266 | 5 |
| 387 | CWE-340 | Generation of Predictable Numbers or Identifiers | The product uses a scheme that generates numbers or identifiers that are more predictable than required. | CWE-331 | 5 |
| 388 | CWE-394 | Unexpected Status Code or Return Value | The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product. | CWE-393 | 5 |
| 389 | CWE-402 | Transmission of Private Resources into a New Sphere ('Resource Leak') | The product makes resources available to untrusted parties when those resources are only intended to be accessed by the product. | | 5 |
| 390 | CWE-646 | Reliance on File Name or Extension of Externally-Supplied File | The product allows a file to be uploaded, but it relies on the file name or extension of the file to determine the appropriate behaviors. This could be used by attackers to cause the file to be misclassified and processed in a dangerous fashion. | | 5 |
| 391 | CWE-656 | Reliance on Security Through Obscurity | The product uses a protection mechanism whose strength depends heavily on its obscurity, such that knowledge of its algorithms or key data is sufficient to defeat the mechanism. | | 5 |
| 392 | CWE-662 | Improper Synchronization | The product utilizes multiple threads or processes to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes. | | 5 |
| 393 | CWE-676 | Use of Potentially Dangerous Function | The product invokes a potentially dangerous function that could introduce a vulnerability if it is used incorrectly, but the function can also be used safely. | | 5 |
| 394 | CWE-779 | Logging of Excessive Data | The product logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack. | CWE-404 | 5 |
| 395 | CWE-790 | Improper Filtering of Special Elements | The product receives data from an upstream component, but does not filter or incorrectly filters special elements before sending it to a downstream component. | CWE-184 | 5 |
| 396 | CWE-842 | Placement of User into Incorrect Group | The product or the administrator places a user into an incorrect group. | | 5 |
| 397 | CWE-87 | Improper Neutralization of Alternate XSS Syntax | The product does not neutralize or incorrectly neutralizes user-controlled input for alternate script syntax. | CWE-79 | 5 |
| 398 | CWE-921 | Storage of Sensitive Data in a Mechanism without Access Control | The product stores sensitive information in a file system or device that does not have built-in access control. | CWE-284 | 5 |
| 399 | CWE-1038 | Insecure Automated Optimizations | The product uses a mechanism that automatically optimizes code, e.g. to improve a characteristic such as performance, but the optimizations can have an unintended side effect that might violate an intended security assumption. | | 4 |
| 400 | CWE-1125 | Excessive Attack Surface | The product has an attack surface whose quantitative measurement exceeds a desirable maximum. | | 4 |
| 401 | CWE-1240 | Use of a Cryptographic Primitive with a Risky Implementation | To fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant cryptographic implementation. | CWE-327 | 4 |
| 402 | CWE-1258 | Exposure of Sensitive System Information Due to Uncleared Debug Information | The hardware does not fully clear security-sensitive values, such as keys and intermediate values in cryptographic operations, when debug mode is entered. | CWE-200 | 4 |
| 403 | CWE-1395 | Dependency on Vulnerable Third-Party Component | The product has a dependency on a third-party component that contains one or more known vulnerabilities. | | 4 |
| 404 | CWE-223 | Omission of Security-relevant Information | The product does not record or display information that would be important for identifying the source or nature of an attack, or determining if an action is safe. | | 4 |
| 405 | CWE-229 | Improper Handling of Values | The product does not properly handle when the expected number of values for parameters, fields, or arguments is not provided in input, or if those values are undefined. | CWE-20 | 4 |
| 406 | CWE-26 | Path Traversal: '/dir/../filename' | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/dir/../filename" sequences that can resolve to a location that is outside of that directory. | CWE-23 | 4 |
| 407 | CWE-278 | Insecure Preserved Inherited Permissions | A product inherits a set of insecure permissions for an object, e.g. when copying from an archive file, without user awareness or involvement. | CWE-266 | 4 |
| 408 | CWE-283 | Unverified Ownership | The product does not properly verify that a critical resource is owned by the proper entity. | CWE-282 | 4 |
| 409 | CWE-299 | Improper Check for Certificate Revocation | The product does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised. | CWE-298 | 4 |
| 410 | CWE-317 | Cleartext Storage of Sensitive Information in GUI | The product stores sensitive information in cleartext within the GUI. | CWE-312 | 4 |
| 411 | CWE-329 | Generation of Predictable IV with CBC Mode | The product generates and uses a predictable initialization Vector (IV) with Cipher Block Chaining (CBC) Mode, which causes algorithms to be susceptible to dictionary attacks when they are encrypted under the same key. | CWE-310 | 4 |
| 412 | CWE-356 | Product UI does not Warn User of Unsafe Actions | The product's user interface does not warn the user before undertaking an unsafe action on behalf of that user. This makes it easier for attackers to trick users into inflicting damage to their system. | | 4 |
| 413 | CWE-37 | Path Traversal: '/absolute/pathname/here' | The product accepts input in the form of a slash absolute path ('/absolute/pathname/here') without appropriate validation, which can allow an attacker to traverse the file system to unintended locations or access arbitrary files. | CWE-36 | 4 |
| 414 | CWE-419 | Unprotected Primary Channel | The product uses a primary channel for administration or restricted functionality, but it does not properly protect the channel. | | 4 |
| 415 | CWE-435 | Improper Interaction Between Multiple Correctly-Behaving Entities | An interaction error occurs when two entities have correct behavior when running independently of each other, but when they are integrated as components in a larger system or process, they introduce incorrect behaviors that may cause resultant weaknesses. | | 4 |
| 416 | CWE-449 | The UI Performs the Wrong Action | The UI performs the wrong action with respect to the user's request. | | 4 |
| 417 | CWE-533 | Information Exposure Through Server Log Files (deprecated) | This entry has been deprecated because its abstraction was too low-level. See CWE-532. | CWE-532 | 4 |
| 418 | CWE-561 | Dead Code | The product contains dead code, which can never be executed. | CWE-18 | 4 |
| 419 | CWE-612 | Improper Authorization of Index Containing Sensitive Information | 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. | | 4 |
| 420 | CWE-626 | Null Byte Interaction Error | The product does not properly handle null bytes or NUL characters when passing data between different representations or components. | | 4 |
| 421 | CWE-643 | Improper Neutralization of Data within XPath Expressions | The product uses external input to dynamically construct an XPath expression used to retrieve data from an XML database, but it does not neutralize or incorrectly neutralizes that input. This allows an attacker to control the structure of the query. | CWE-74 | 4 |
| 422 | CWE-708 | Incorrect Ownership Assignment | The product assigns an owner to a resource, but the owner is outside of the intended control sphere. | CWE-285 | 4 |
| 423 | CWE-760 | Use of a One-Way Hash with a Predictable Salt | The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product uses a predictable salt as part of the input. | CWE-759 | 4 |
| 424 | CWE-782 | Exposed IOCTL with Insufficient Access Control | The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL. | | 4 |
| 425 | CWE-791 | Incomplete Filtering of Special Elements | The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component. | CWE-790 | 4 |
| 426 | CWE-84 | Improper Neutralization of Encoded URI Schemes in a Web Page | The web application improperly neutralizes user-controlled input for executable script disguised with URI encodings. | CWE-79 | 4 |
| 427 | CWE-1025 | Comparison Using Wrong Factors | The code performs a comparison between two entities, but the comparison examines the wrong factors or characteristics of the entities, which can lead to incorrect results and resultant weaknesses. | | 3 |
| 428 | CWE-1050 | Excessive Platform Resource Consumption within a Loop | The product has a loop body or loop condition that contains a control element that directly or indirectly consumes platform resources, e.g. messaging, sessions, locks, or file descriptors. | CWE-400 | 3 |
| 429 | CWE-1088 | Synchronous Access of Remote Resource without Timeout | 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. | | 3 |
| 430 | CWE-112 | Missing XML Validation | The product accepts XML from an untrusted source but does not validate the XML against the proper schema. | | 3 |
| 431 | CWE-1241 | Use of Predictable Algorithm in Random Number Generator | The device uses an algorithm that is predictable and generates a pseudo-random number. | CWE-338 | 3 |
| 432 | CWE-1245 | Improper Finite State Machines in Hardware Logic | Faulty finite state machines (FSMs) in the hardware logic allow an attacker to put the system in an undefined state, to cause a denial of service (DoS) or gain privileges on the victim's system. | | 3 |
| 433 | CWE-1250 | Improper Preservation of Consistency Between Independent Representations of Shared State | The product has or supports multiple distributed components or sub-systems that are each required to keep their own local copy of shared data - such as state or cache - but the product does not ensure that all local copies remain consistent with each other. | | 3 |
| 434 | CWE-1259 | Improper Restriction of Security Token Assignment | The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected. | | 3 |
| 435 | CWE-1281 | Sequence of Processor Instructions Leads to Unexpected Behavior | Specific combinations of processor instructions lead to undesirable behavior such as locking the processor until a hard reset performed. | | 3 |
| 436 | CWE-1325 | Improperly Controlled Sequential Memory Allocation | The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects. | | 3 |
| 437 | CWE-1357 | Reliance on Uncontrolled Component | The product is built from multiple separate components, but it uses a component that is not sufficiently trusted to meet expectations for security, reliability, updateability, and maintainability. | | 3 |
| 438 | CWE-167 | Improper Handling of Additional Special Element | The product receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided. | CWE-20 | 3 |
| 439 | CWE-177 | Improper Handling of URL Encoding | The product does not properly handle when all or part of an input has been URL encoded. | CWE-172 | 3 |
| 440 | CWE-180 | Incorrect Behavior Order: Validate Before Canonicalize | The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step. | CWE-179 | 3 |
| 441 | CWE-232 | Improper Handling of Undefined Values | The product does not handle or incorrectly handles when a value is not defined or supported for the associated parameter, field, or argument name. | CWE-229 | 3 |
| 442 | CWE-237 | Improper Handling of Structural Elements | The product does not handle or incorrectly handles inputs that are related to complex structures. | CWE-229 | 3 |
| 443 | CWE-242 | Use of Inherently Dangerous Function | The product calls a function that can never be guaranteed to work safely. | CWE-18 | 3 |
| 444 | CWE-28 | Path Traversal: '..\filedir' | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "..\" sequences that can resolve to a location that is outside of that directory. | CWE-23 | 3 |
| 445 | CWE-291 | Reliance on IP Address for Authentication | The product uses an IP address for authentication. | CWE-287 | 3 |
| 446 | CWE-296 | Improper Following of a Certificate's Chain of Trust | The product does not follow, or incorrectly follows, the chain of trust for a certificate back to a trusted root certificate, resulting in incorrect trust of any resource that is associated with that certificate. | CWE-295 | 3 |
| 447 | CWE-314 | Cleartext Storage in the Registry | The product stores sensitive information in cleartext in the registry. | CWE-312 | 3 |
| 448 | CWE-318 | Cleartext Storage of Sensitive Information in Executable | The product stores sensitive information in cleartext in an executable. | CWE-312 | 3 |
| 449 | CWE-336 | Same Seed in Pseudo-Random Number Generator | A Pseudo-Random Number Generator (PRNG) uses the same seed each time the product is initialized. | CWE-331 | 3 |
| 450 | CWE-342 | Predictable Exact Value from Previous Values | An exact value or random number can be precisely predicted by observing previous values. | CWE-341 | 3 |
| 451 | CWE-343 | Predictable Value Range from Previous Values | The product's random number generator produces a series of values which, when observed, can be used to infer a relatively small range of possibilities for the next value that could be generated. | CWE-342 | 3 |
| 452 | CWE-351 | Insufficient Type Distinction | The product does not properly distinguish between different types of elements in a way that leads to insecure behavior. | | 3 |
| 453 | CWE-363 | Race Condition Enabling Link Following | The product checks the status of a file or directory before accessing it, which produces a race condition in which the file can be replaced with a link before the access is performed, causing the product to access the wrong file. | CWE-362 | 3 |
| 454 | CWE-364 | Signal Handler Race Condition | The product uses a signal handler that introduces a race condition. | CWE-362 | 3 |
| 455 | CWE-390 | Detection of Error Condition Without Action | The product detects a specific error, but takes no actions to handle the error. | | 3 |
| 456 | CWE-412 | Unrestricted Externally Accessible Lock | The product properly checks for the existence of a lock, but the lock can be externally controlled or influenced by an actor that is outside of the intended sphere of control. | CWE-404 | 3 |
| 457 | CWE-421 | Race Condition During Access to Alternate Channel | The product opens an alternate channel to communicate with an authorized user, but the channel is accessible to other actors. | | 3 |
| 458 | CWE-447 | Unimplemented or Unsupported Feature in UI | A UI function for a security feature appears to be supported and gives feedback to the user that suggests that it is supported, but the underlying functionality is not implemented. | | 3 |
| 459 | CWE-514 | Covert Channel | A covert channel is a path that can be used to transfer information in a way not intended by the system's designers. | | 3 |
| 460 | CWE-526 | Exposure of Sensitive Information Through Environmental Variables | The product uses an environment variable to store unencrypted sensitive information. | CWE-200 | 3 |
| 461 | CWE-544 | Missing Standardized Error Handling Mechanism | The product does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses. | | 3 |
| 462 | CWE-564 | SQL Injection Hibernate | Using Hibernate to execute a dynamic SQL statement built with user-controlled input can allow an attacker to modify the statement's meaning or to execute arbitrary SQL commands. | CWE-89 | 3 |
| 463 | CWE-590 | Free of Memory not on the Heap | The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc(). | | 3 |
| 464 | CWE-606 | Unchecked Input for Loop Condition | 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. | CWE-404 | 3 |
| 465 | CWE-65 | Windows Hard Link | The product, when opening a file or directory, does not sufficiently handle when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. | CWE-64 | 3 |
| 466 | CWE-655 | Insufficient Psychological Acceptability | The product has a protection mechanism that is too difficult or inconvenient to use, encouraging non-malicious users to disable or bypass the mechanism, whether by accident or on purpose. | | 3 |
| 467 | CWE-762 | Mismatched Memory Management Routines | The product attempts to return a memory resource to the system, but it calls a release function that is not compatible with the function that was originally used to allocate that resource. | CWE-119 | 3 |
| 468 | CWE-783 | Operator Precedence Logic Error | The product uses an expression in which operator precedence causes incorrect logic to be used. | | 3 |
| 469 | CWE-784 | Reliance on Cookies without Validation and Integrity Checking in a Security Decision | The product uses a protection mechanism that relies on the existence or values of a cookie, but it does not properly ensure that the cookie is valid for the associated user. | | 3 |
| 470 | CWE-792 | Incomplete Filtering of One or More Instances of Special Elements | The product receives data from an upstream component, but does not completely filter one or more instances of special elements before sending it to a downstream component. | CWE-790 | 3 |
| 471 | CWE-820 | Missing Synchronization | The product utilizes a shared resource in a concurrent manner but does not attempt to synchronize access to the resource. | CWE-821 | 3 |
| 472 | CWE-826 | Premature Release of Resource During Expected Lifetime | The product releases a resource that is still intended to be used by itself or another actor. | | 3 |
| 473 | CWE-83 | Improper Neutralization of Script in Attributes in a Web Page | The product does not neutralize or incorrectly neutralizes "javascript:" or other URIs from dangerous attributes within tags, such as onmouseover, onload, onerror, or style. | CWE-79 | 3 |
| 474 | CWE-838 | Inappropriate Encoding for Output Context | The product uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component. | | 3 |
| 475 | CWE-941 | Incorrectly Specified Destination in a Communication Channel | The product creates a communication channel to initiate an outgoing request to an actor, but it does not correctly specify the intended destination for that actor. | | 3 |
| 476 | CWE-1007 | Insufficient Visual Distinction of Homoglyphs Presented to User | The product displays information or identifiers to a user, but the display mechanism does not make it easy for the user to distinguish between visually similar or identical glyphs (homoglyphs), which may cause the user to misinterpret a glyph and perform an unintended, insecure action. | | 2 |
| 477 | CWE-1049 | Excessive Data Query Operations in a Large Data Table | The product performs a data query with a large number of joins and sub-queries on a large data table. | CWE-400 | 2 |
| 478 | CWE-1077 | Floating Point Comparison with Incorrect Operator | 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. | | 2 |
| 479 | CWE-1100 | Insufficient Isolation of System-Dependent Functions | The product or code does not isolate system-dependent functionality into separate standalone modules. | | 2 |
| 480 | CWE-1103 | Use of Platform-Dependent Third Party Components | The product relies on third-party components that do not provide equivalent functionality across all desirable platforms. | | 2 |
| 481 | CWE-1107 | Insufficient Isolation of Symbolic Constant Definitions | The source code uses symbolic constants, but it does not sufficiently place the definitions of these constants into a more centralized or isolated location. | | 2 |
| 482 | CWE-1108 | Excessive Reliance on Global Variables | The code is structured in a way that relies too much on using or setting global variables throughout various points in the code, instead of preserving the associated information in a narrower, more local context. | | 2 |
| 483 | CWE-1173 | Improper Use of Validation Framework | The product does not use, or incorrectly uses, an input validation framework that is provided by the source language or an independent library. | CWE-20 | 2 |
| 484 | CWE-1189 | Improper Isolation of Shared Resources on System-on-a-Chip (SoC) | The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents. | | 2 |
| 485 | CWE-1234 | Hardware Internal or Debug Modes Allow Override of Locks | System configuration protection may be bypassed during debug mode. | CWE-489 | 2 |
| 486 | CWE-1244 | Internal Asset Exposed to Unsafe Debug Access Level or State | The product uses physical debug or test interfaces with support for multiple access levels, but it assigns the wrong debug access level to an internal asset, providing unintended access to the asset from untrusted debug agents. | CWE-489 | 2 |
| 487 | CWE-1247 | Improper Protection Against Voltage and Clock Glitches | The device does not contain or contains incorrectly implemented circuitry or sensors to detect and mitigate voltage and clock glitches and protect sensitive information or software contained on the device. | | 2 |
| 488 | CWE-1251 | Mirrored Regions with Different Values | The product's architecture mirrors regions without ensuring that their contents always stay in sync. | | 2 |
| 489 | CWE-1255 | Comparison Logic is Vulnerable to Power Side-Channel Attacks | A device's real time power consumption may be monitored during security token evaluation and the information gleaned may be used to determine the value of the reference token. | CWE-203 | 2 |
| 490 | CWE-1256 | Improper Restriction of Software Interfaces to Hardware Features | The product provides software-controllable device functionality for capabilities such as power and clock management, but it does not properly limit functionality that can lead to modification of hardware memory or register bits, or the ability to observe physical side channels. | | 2 |
| 491 | CWE-1269 | Product Released in Non-Release Configuration | The product released to market is released in pre-production or manufacturing configuration. | | 2 |
| 492 | CWE-127 | Buffer Under-read | The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations prior to the targeted buffer. | CWE-119 | 2 |
| 493 | CWE-1270 | Generation of Incorrect Security Tokens | The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect. | | 2 |
| 494 | CWE-1274 | Improper Access Control for Volatile Memory Containing Boot Code | The product conducts a secure-boot process that transfers bootloader code from Non-Volatile Memory (NVM) into Volatile Memory (VM), but it does not have sufficient access control or other protections for the Volatile Memory. | CWE-284 | 2 |
| 495 | CWE-1289 | Improper Validation of Unsafe Equivalence in Input | The product receives an input value that is used as a resource identifier or other type of reference, but it does not validate or incorrectly validates that the input is equivalent to a potentially-unsafe value. | CWE-20 | 2 |
| 496 | CWE-1319 | Improper Protection against Electromagnetic Fault Injection (EM-FI) | The device is susceptible to electromagnetic fault injection attacks, causing device internal information to be compromised or security mechanisms to be bypassed. | CWE-74 | 2 |
| 497 | CWE-1323 | Improper Management of Sensitive Trace Data | Trace data collected from several sources on the System-on-Chip (SoC) is stored in unprotected locations or transported to untrusted agents. | CWE-200 | 2 |
| 498 | CWE-1332 | Improper Handling of Faults that Lead to Instruction Skips | The device is missing or incorrectly implements circuitry or sensors that detect and mitigate the skipping of security-critical CPU instructions when they occur. | CWE-404 | 2 |
| 499 | CWE-141 | Improper Neutralization of Parameter/Argument Delimiters | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as parameter or argument delimiters when they are sent to a downstream component. | CWE-140 | 2 |
| 500 | CWE-1419 | Incorrect Initialization of Resource | The product attempts to initialize a resource but does not correctly do so, which might leave the resource in an unexpected, incorrect, or insecure state when it is accessed. | CWE-665 | 2 |
| 501 | CWE-142 | Improper Neutralization of Value Delimiters | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as value delimiters when they are sent to a downstream component. | CWE-140 | 2 |
| 502 | CWE-149 | Improper Neutralization of Quoting Syntax | Quotes injected into a product can be used to compromise a system. As data are parsed, an injected/absent/duplicate/malformed use of quotes may cause the process to take unexpected actions. | CWE-20 | 2 |
| 503 | CWE-159 | Improper Handling of Invalid Use of Special Elements | The product does not properly filter, remove, quote, or otherwise manage the invalid use of special elements in user-controlled input, which could cause adverse effect on its behavior and integrity. | CWE-20 | 2 |
| 504 | CWE-168 | Improper Handling of Inconsistent Special Elements | The product does not properly handle input in which an inconsistency exists between two or more special characters or reserved words. | CWE-20 | 2 |
| 505 | CWE-179 | Incorrect Behavior Order: Early Validation | The product validates input before applying protection mechanisms that modify the input, which could allow an attacker to bypass the validation via dangerous inputs that only arise after the modification. | CWE-20 | 2 |
| 506 | CWE-196 | Unsigned to Signed Conversion Error | The product uses an unsigned primitive and performs a cast to a signed primitive, which can produce an unexpected value if the value of the unsigned primitive can not be represented using a signed primitive. | CWE-194 | 2 |
| 507 | CWE-216 | Containment Errors (deprecated) | This entry has been deprecated, as it was not effective as a weakness and was structured more like a category. In addition, the name is inappropriate, since the "container" term is widely understood by developers in different ways than originally intended by PLOVER, the original source for this entry. | | 2 |
| 508 | CWE-219 | Storage of File with Sensitive Data Under Web Root | The product stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties. | CWE-200 | 2 |
| 509 | CWE-221 | Information Loss or Omission | The product does not record, or improperly records, security-relevant information that leads to an incorrect decision or hampers later analysis. | | 2 |
| 510 | CWE-231 | Improper Handling of Extra Values | The product does not handle or incorrectly handles when more values are provided than expected. | CWE-229 | 2 |
| 511 | CWE-235 | Improper Handling of Extra Parameters | The product does not handle or incorrectly handles when the number of parameters, fields, or arguments with the same name exceeds the expected amount. | CWE-233 | 2 |
| 512 | CWE-244 | Improper Clearing of Heap Memory Before Release | Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory. | | 2 |
| 513 | CWE-298 | Improper Validation of Certificate Expiration | A certificate expiration is not validated or is incorrectly validated, so trust may be assigned to certificates that have been abandoned due to age. | CWE-295 | 2 |
| 514 | CWE-32 | Path Traversal: '...' (Triple Dot) | The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '...' (triple dot) sequences that can resolve to a location that is outside of that directory. | CWE-23 | 2 |
| 515 | CWE-337 | Predictable Seed in Pseudo-Random Number Generator (PRNG) | A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time. | CWE-331 | 2 |
| 516 | CWE-344 | Use of Invariant Value in Dynamically Changing Context | The product uses a constant value, name, or reference, but this value can (or should) vary across different environments. | | 2 |
| 517 | CWE-365 | Race Condition in Switch (deprecated) | This entry has been deprecated. There are no documented cases in which a switch's control expression is evaluated more than once. | CWE-362 | 2 |
| 518 | CWE-392 | Missing Report of Error Condition | The product encounters an error but does not provide a status code or return value to indicate that an error has occurred. | | 2 |
| 519 | CWE-393 | Return of Wrong Status Code | A function or operation returns an incorrect return value or status code that does not indicate an error, but causes the product to modify its behavior based on the incorrect result. | | 2 |
| 520 | CWE-413 | Improper Resource Locking | The product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource. | CWE-404 | 2 |
| 521 | CWE-422 | Unprotected Windows Messaging Channel | The product does not properly verify the source of a message in the Windows Messaging System while running at elevated privileges, creating an alternate channel through which an attacker can directly send a message to the product. | CWE-419 | 2 |
| 522 | CWE-446 | UI Discrepancy for Security Feature | The user interface does not correctly enable or configure a security feature, but the interface provides feedback that causes the user to believe that the feature is in a secure state. | | 2 |
| 523 | CWE-467 | Use of sizeof() on a Pointer Type | The code calls sizeof() on a malloced pointer type, which always returns the wordsize/8. This can produce an unexpected result if the programmer intended to determine how much memory has been allocated. | | 2 |
| 524 | CWE-468 | Incorrect Pointer Scaling | In C and C++, one may often accidentally refer to the wrong memory due to the semantics of when math operations are implicitly scaled. | | 2 |
| 525 | CWE-473 | PHP External Variable Modification | A PHP application does not properly protect against the modification of variables from external sources, such as query parameters or cookies. This can expose the application to numerous weaknesses that would not exist otherwise. | | 2 |
| 526 | CWE-527 | Exposure of Version-Control Repository to an Unauthorized Control Sphere | The product stores a CVS, git, or other repository in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors. | CWE-285 | 2 |
| 527 | CWE-550 | Server-generated Error Message Containing Sensitive Information | Certain conditions, such as network failure, will cause a server error message to be displayed. | CWE-200 | 2 |
| 528 | CWE-562 | Return of Stack Variable Address | A function returns the address of a stack variable, which will cause unintended program behavior, typically in the form of a crash. | | 2 |
| 529 | CWE-592 | Authentication Bypass Issues (deprecated) | This weakness has been deprecated because it covered redundant concepts already described in CWE-287. | CWE-287 | 2 |
| 530 | CWE-597 | Use of Wrong Operator in String Comparison | The product uses the wrong operator when comparing a string, such as using "==" when the .equals() method should be used instead. | CWE-697 | 2 |
| 531 | CWE-62 | UNIX Hard Link | The product, when opening a file or directory, does not sufficiently account for when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. | CWE-61 | 2 |
| 532 | CWE-622 | Improper Validation of Function Hook Arguments | The product adds hooks to user-accessible API functions, but it does not properly validate the arguments. This could lead to resultant vulnerabilities. | | 2 |
| 533 | CWE-625 | Permissive Regular Expression | The product uses a regular expression that does not sufficiently restrict the set of allowed values. | CWE-185 | 2 |
| 534 | CWE-627 | Dynamic Variable Evaluation | In a language where the user can influence the name of a variable at runtime, if the variable names are not controlled, an attacker can read or write to arbitrary variables, or access arbitrary functions. | | 2 |
| 535 | CWE-645 | Overly Restrictive Account Lockout Mechanism | The product contains an account lockout protection mechanism, but the mechanism is too restrictive and can be triggered too easily, which allows attackers to deny service to legitimate users by causing their accounts to be locked out. | CWE-404 | 2 |
| 536 | CWE-687 | Function Call With Incorrectly Specified Argument Value | The product calls a function, procedure, or routine, but the caller specifies an argument that contains the wrong value, which may lead to resultant weaknesses. | | 2 |
| 537 | CWE-710 | Improper Adherence to Coding Standards | The product does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities. | CWE-17 | 2 |
| 538 | CWE-756 | Missing Custom Error Page | The product does not return custom error pages to the user, possibly exposing sensitive information. | CWE-209 | 2 |
| 539 | CWE-767 | Access to Critical Private Variable via Public Method | The product defines a public method that reads or modifies a private variable. | | 2 |
| 540 | CWE-774 | Allocation of File Descriptors or Handles Without Limits or Throttling | The product allocates file descriptors or handles on behalf of an actor without imposing any restrictions on how many descriptors can be allocated, in violation of the intended security policy for that actor. | | 2 |
| 541 | CWE-775 | Missing Release of File Descriptor or Handle after Effective Lifetime | The product does not release a file descriptor or handle after its effective lifetime has ended, i.e., after the file descriptor/handle is no longer needed. | CWE-400 | 2 |
| 542 | CWE-780 | Use of RSA Algorithm without OAEP | The product uses the RSA algorithm but does not incorporate Optimal Asymmetric Encryption Padding (OAEP), which might weaken the encryption. | CWE-326 | 2 |
| 543 | CWE-81 | Improper Neutralization of Script in an Error Message Web Page | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters that could be interpreted as web-scripting elements when they are sent to an error page. | CWE-79 | 2 |
| 544 | CWE-830 | Inclusion of Web Functionality from an Untrusted Source | The product includes web functionality (such as a web widget) from another domain, which causes it to operate within the domain of the product, potentially granting total access and control of the product to the untrusted source. | CWE-829 | 2 |
| 545 | CWE-85 | Doubled Character XSS Manipulations | The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters. | CWE-79 | 2 |
| 546 | CWE-86 | Improper Neutralization of Invalid Characters in Identifiers in Web Pages | The product does not neutralize or incorrectly neutralizes invalid characters or byte sequences in the middle of tag names, URI schemes, and other identifiers. | CWE-79 | 2 |
| 547 | CWE-914 | Improper Control of Dynamically-Identified Variables | The product does not properly restrict reading from or writing to dynamically-identified variables. | CWE-913 | 2 |
| 548 | CWE-97 | Improper Neutralization of Server-Side Includes (SSI) Within a Web Page | The product generates a web page, but does not neutralize or incorrectly neutralizes user-controllable input that could be interpreted as a server-side include (SSI) directive. | CWE-20 | 2 |
| 549 | CWE-20 | Improper Input Validation | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. | | 1 |
| 550 | CWE-1023 | Incomplete Comparison with Missing Factors | The product performs a comparison between entities that must consider multiple factors or characteristics of each entity, but the comparison does not include one or more of these factors. | | 1 |
| 551 | CWE-1037 | Processor Optimization Removal or Modification of Security-critical Code | The developer builds a security-critical protection mechanism into the software, but the processor optimizes the execution of the program such that the mechanism is removed or modified. | | 1 |
| 552 | CWE-1051 | Initialization with Hard-Coded Network Resource Configuration Data | The product initializes data using hard-coded values that act as network resource identifiers. | | 1 |
| 553 | CWE-1057 | Data Access Operations Outside of Expected Data Manager Component | 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. | | 1 |
| 554 | CWE-1059 | Insufficient Technical Documentation | 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. | | 1 |
| 555 | CWE-1068 | Inconsistency Between Implementation and Documented Design | The implementation of the product is not consistent with the design as described within the relevant documentation. | CWE-1059 | 1 |
| 556 | CWE-1083 | Data Access from Outside Expected Data Manager Component | 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. | | 1 |
| 557 | CWE-11 | ASP.NET Misconfiguration: Creating Debug Binary | Debugging messages help attackers learn about the system and plan a form of attack. | | 1 |
| 558 | CWE-1112 | Incomplete Documentation of Program Execution | The document does not fully define all mechanisms that are used to control or influence how product-specific programs are executed. | CWE-1110 | 1 |
| 559 | CWE-1190 | DMA Device Enabled Too Early in Boot Phase | The product enables a Direct Memory Access (DMA) capable device before the security configuration settings are established, which allows an attacker to extract data from or gain privileges on the product. | | 1 |
| 560 | CWE-12 | ASP.NET Misconfiguration: Missing Custom Error Page | An ASP .NET application must enable custom error pages in order to prevent attackers from mining information from the framework's built-in responses. | CWE-756 | 1 |
| 561 | CWE-1222 | Insufficient Granularity of Address Regions Protected by Register Locks | The product defines a large address region protected from modification by the same register lock control bit. This results in a conflict between the functional requirement that some addresses need to be writable by software during operation and the security requirement that the system configuration lock bit must be set during the boot process. | | 1 |
| 562 | CWE-1231 | Improper Prevention of Lock Bit Modification | The product uses a trusted lock bit for restricting access to registers, address regions, or other resources, but the product does not prevent the value of the lock bit from being modified after it has been set. | | 1 |
| 563 | CWE-1233 | Security-Sensitive Hardware Controls with Missing Lock Bit Protection | The product uses a register lock bit protection mechanism, but it does not ensure that the lock bit prevents modification of system registers or controls that perform changes to important hardware system configuration. | | 1 |
| 564 | CWE-1246 | Improper Write Handling in Limited-write Non-Volatile Memories | The product does not implement or incorrectly implements wear leveling operations in limited-write non-volatile memories. | | 1 |
| 565 | CWE-1253 | Incorrect Selection of Fuse Values | The logic level used to set a system to a secure state relies on a fuse being unblown. An attacker can set the system to an insecure state merely by blowing the fuse. | | 1 |
| 566 | CWE-1260 | Improper Handling of Overlap Between Protected Memory Ranges | The product allows address regions to overlap, which can result in the bypassing of intended memory protection. | CWE-119 | 1 |
| 567 | CWE-1262 | Improper Access Control for Register Interface | The product uses memory-mapped I/O registers that act as an interface to hardware functionality from software, but there is improper access control to those registers. | CWE-284 | 1 |
| 568 | CWE-1264 | Hardware Logic with Insecure De-Synchronization between Control and Data Channels | The hardware logic for error handling and security checks can incorrectly forward data before the security check is complete. | | 1 |
| 569 | CWE-1272 | Sensitive Information Uncleared Before Debug/Power State Transition | The product performs a power or debug state transition, but it does not clear sensitive information that should no longer be accessible due to changes to information access restrictions. | CWE-200 | 1 |
| 570 | CWE-1282 | Assumed-Immutable Data is Stored in Writable Memory | Immutable data, such as a first-stage bootloader, device identifiers, and "write-once" configuration settings are stored in writable memory that can be re-programmed or updated in the field. | | 1 |
| 571 | CWE-1283 | Mutable Attestation or Measurement Reporting Data | The register contents used for attestation or measurement reporting data to verify boot flow are modifiable by an adversary. | | 1 |
| 572 | CWE-1298 | Hardware Logic Contains Race Conditions | A race condition in the hardware logic results in undermining security guarantees of the system. | CWE-362 | 1 |
| 573 | CWE-1303 | Non-Transparent Sharing of Microarchitectural Resources | Hardware structures shared across execution contexts (e.g., caches and branch predictors) can violate the expected architecture isolation between contexts. | | 1 |
| 574 | CWE-1304 | Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation | The product performs a power save/restore operation, but it does not ensure that the integrity of the configuration state is maintained and/or verified between the beginning and ending of the operation. | | 1 |
| 575 | CWE-132 | Miscalculated Null Termination (deprecated) | This entry has been deprecated because it was a duplicate of CWE-170. All content has been transferred to CWE-170. | CWE-119 | 1 |
| 576 | CWE-1328 | Security Version Number Mutable to Older Versions | Security-version number in hardware is mutable, resulting in the ability to downgrade (roll-back) the boot firmware to vulnerable code versions. | | 1 |
| 577 | CWE-1329 | Reliance on Component That is Not Updateable | The product contains a component that cannot be updated or patched in order to remove vulnerabilities or significant bugs. | | 1 |
| 578 | CWE-1341 | Multiple Releases of Same Resource or Handle | The product attempts to close or release a resource or handle more than once, without any successful open between the close operations. | | 1 |
| 579 | CWE-1384 | Improper Handling of Extreme Physical Environment Conditions | The product does not properly handle unexpected physical or environmental conditions that occur naturally or are artificially induced. | CWE-388 | 1 |
| 580 | CWE-1389 | Incorrect Parsing of Numbers with Different Radices | The product parses numeric input assuming base 10 (decimal) values, but it does not account for inputs that use a different base number (radix). | | 1 |
| 581 | CWE-144 | Improper Neutralization of Line Delimiters | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as line delimiters when they are sent to a downstream component. | CWE-140 | 1 |
| 582 | CWE-147 | Improper Neutralization of Input Terminators | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as input terminators when they are sent to a downstream component. | CWE-140 | 1 |
| 583 | CWE-154 | Improper Neutralization of Variable Name Delimiters | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as variable name delimiters when they are sent to a downstream component. | CWE-20 | 1 |
| 584 | CWE-164 | Improper Neutralization of Internal Special Elements | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes internal special elements that could be interpreted in unexpected ways when they are sent to a downstream component. | CWE-20 | 1 |
| 585 | CWE-166 | Improper Handling of Missing Special Element | The product receives input from an upstream component, but it does not handle or incorrectly handles when an expected special element is missing. | CWE-20 | 1 |
| 586 | CWE-173 | Improper Handling of Alternate Encoding | The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent. | CWE-172 | 1 |
| 587 | CWE-174 | Double Decoding of the Same Data | The product decodes the same input twice, which can limit the effectiveness of any protection mechanism that occurs in between the decoding operations. | CWE-172 | 1 |
| 588 | CWE-182 | Collapse of Data into Unsafe Value | The product filters data in a way that causes it to be reduced or "collapsed" into an unsafe value that violates an expected security property. | | 1 |
| 589 | CWE-194 | Unexpected Sign Extension | The product performs an operation on a number that causes it to be sign extended when it is transformed into a larger data type. When the original number is negative, this can produce unexpected values that lead to resultant weaknesses. | CWE-189 | 1 |
| 590 | CWE-206 | Observable Internal Behavioral Discrepancy | The product performs multiple behaviors that are combined to produce a single result, but the individual behaviors are observable separately in a way that allows attackers to reveal internal state or internal decision points. | CWE-203 | 1 |
| 591 | CWE-210 | Self-generated Error Message Containing Sensitive Information | The product identifies an error condition and creates its own diagnostic or error messages that contain sensitive information. | CWE-209 | 1 |
| 592 | CWE-224 | Obscured Security-relevant Information by Alternate Name | The product records security-relevant information according to an alternate name of the affected entity, instead of the canonical name. | | 1 |
| 593 | CWE-236 | Improper Handling of Undefined Parameters | The product does not handle or incorrectly handles when a particular parameter, field, or argument name is not defined or supported by the product. | CWE-233 | 1 |
| 594 | CWE-239 | Failure to Handle Incomplete Element | The product does not properly handle when a particular element is not completely specified. | CWE-229 | 1 |
| 595 | CWE-263 | Password Aging with Long Expiration | The product supports password aging, but the expiration period is too long. | CWE-262 | 1 |
| 596 | CWE-292 | Trusting Self-reported DNS Name (deprecated) | This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350. | CWE-287 | 1 |
| 597 | CWE-315 | Cleartext Storage of Sensitive Information in a Cookie | The product stores sensitive information in cleartext in a cookie. | CWE-312 | 1 |
| 598 | CWE-360 | Trust of System Event Data | Security based on event locations are insecure and can be spoofed. | | 1 |
| 599 | CWE-368 | Context Switching Race Condition | A product performs a series of non-atomic actions to switch between contexts that cross privilege or other security boundaries, but a race condition allows an attacker to modify or misrepresent the product's behavior during the switch. | CWE-362 | 1 |
| 600 | CWE-372 | Incomplete Internal State Distinction | The product does not properly determine which state it is in, causing it to assume it is in state X when in fact it is in state Y, causing it to perform incorrect operations in a security-relevant manner. | CWE-371 | 1 |
| 601 | CWE-38 | Path Traversal: '\absolute\pathname\here' | The product accepts input in the form of a backslash absolute path ('\absolute\pathname\here') without appropriate validation, which can allow an attacker to traverse the file system to unintended locations or access arbitrary files. | CWE-36 | 1 |
| 602 | CWE-40 | Path Traversal: '\\UNC\share\name\' (Windows UNC Share) | The product accepts input that identifies a Windows UNC share ('\\UNC\share\name') that potentially redirects access to an unintended location or arbitrary file. | CWE-22 | 1 |
| 603 | CWE-403 | Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak') | A process does not close sensitive file descriptors before invoking a child process, which allows the child to perform unauthorized I/O operations using those descriptors. | | 1 |
| 604 | CWE-408 | Incorrect Behavior Order: Early Amplification | The product allows an entity to perform a legitimate but expensive operation before authentication or authorization has taken place. | CWE-405 | 1 |
| 605 | CWE-414 | Missing Lock Check | A product does not check to see if a lock is present before performing sensitive operations on a resource. | CWE-404 | 1 |
| 606 | CWE-437 | Incomplete Model of Endpoint Features | A product acts as an intermediary or monitor between two or more endpoints, but it does not have a complete model of an endpoint's features, behaviors, or state, potentially causing the product to perform incorrect actions based on this incomplete model. | | 1 |
| 607 | CWE-44 | Path Equivalence: 'file.name' (Internal Dot) | The product accepts path input in the form of internal dot ('file.ordir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files. | CWE-41 | 1 |
| 608 | CWE-450 | Multiple Interpretations of UI Input | The UI has multiple interpretations of user input but does not prompt the user when it selects the less secure interpretation. | | 1 |
| 609 | CWE-455 | Non-exit on Failed Initialization | The product does not exit or otherwise modify its operation when security-relevant errors occur during initialization, such as when a configuration file has a format error or a hardware security module (HSM) cannot be activated, which can cause the product to execute in a less secure fashion than intended by the administrator. | CWE-453 | 1 |
| 610 | CWE-466 | Return of Pointer Value Outside of Expected Range | A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference. | CWE-119 | 1 |
| 611 | CWE-480 | Use of Incorrect Operator | The product accidentally uses the wrong operator, which changes the logic in security-relevant ways. | | 1 |
| 612 | CWE-499 | Serializable Class Containing Sensitive Data | The code contains a class with sensitive data, but the class does not explicitly deny serialization. The data can be accessed by serializing the class through another class. | | 1 |
| 613 | CWE-50 | Path Equivalence: '//multiple/leading/slash' | The product accepts path input in the form of multiple leading slash ('//multiple/leading/slash') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files. | CWE-41 | 1 |
| 614 | CWE-520 | .NET Misconfiguration: Use of Impersonation | Allowing a .NET application to run at potentially escalated levels of access to the underlying operating and file systems can be dangerous and result in various forms of attacks. | | 1 |
| 615 | CWE-528 | Exposure of Core Dump File to an Unauthorized Control Sphere | The product generates a core dump file in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors. | CWE-285 | 1 |
| 616 | CWE-531 | Inclusion of Sensitive Information in Test Code | Accessible test applications can pose a variety of security risks. Since developers or administrators rarely consider that someone besides themselves would even know about the existence of these applications, it is common for them to contain sensitive information or functions. | CWE-200 | 1 |
| 617 | CWE-539 | Use of Persistent Cookies Containing Sensitive Information | The web application uses persistent cookies, but the cookies contain sensitive information. | CWE-200 | 1 |
| 618 | CWE-563 | Assignment to Variable without Use | The variable's value is assigned but never used, making it a dead store. | | 1 |
| 619 | CWE-566 | Authorization Bypass Through User-Controlled SQL Primary Key | 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. | CWE-285 | 1 |
| 620 | CWE-567 | Unsynchronized Access to Shared Data in a Multithreaded Context | The product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes. | | 1 |
| 621 | CWE-570 | Expression is Always False | The product contains an expression that will always evaluate to false. | CWE-697 | 1 |
| 622 | CWE-571 | Expression is Always True | The product contains an expression that will always evaluate to true. | CWE-697 | 1 |
| 623 | CWE-573 | Improper Following of Specification by Caller | The product does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform. | | 1 |
| 624 | CWE-587 | Assignment of a Fixed Address to a Pointer | The product sets a pointer to a specific address other than NULL or 0. | | 1 |
| 625 | CWE-595 | Comparison of Object References Instead of Object Contents | The product compares object references instead of the contents of the objects themselves, preventing it from detecting equivalent objects. | | 1 |
| 626 | CWE-599 | Missing Validation of OpenSSL Certificate | 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. | CWE-295 | 1 |
| 627 | CWE-600 | Uncaught Exception in Servlet | The Servlet does not catch all exceptions, which may reveal sensitive debugging information. | | 1 |
| 628 | CWE-615 | Inclusion of Sensitive Information in Source Code Comments | 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. | CWE-18 | 1 |
| 629 | CWE-616 | Incomplete Identification of Uploaded File Variables | 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. | | 1 |
| 630 | CWE-618 | Exposed Unsafe ActiveX Method | An ActiveX control is intended for use in a web browser, but it exposes dangerous methods that perform actions that are outside of the browser's security model (e.g. the zone or domain). | | 1 |
| 631 | CWE-647 | Use of Non-Canonical URL Paths for Authorization Decisions | The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical. This can allow a non-canonical URL to bypass the authorization. | | 1 |
| 632 | CWE-649 | Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking | The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified. | CWE-325 | 1 |
| 633 | CWE-66 | Improper Handling of File Names that Identify Virtual Resources | The product does not handle or incorrectly handles a file name that identifies a "virtual" resource that is not directly specified within the directory that is associated with the file name, causing the product to perform file-based operations on a resource that is not a file. | | 1 |
| 634 | CWE-67 | Improper Handling of Windows Device Names | The product constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a Windows device name such as AUX or CON. This typically leads to denial of service or an information exposure when the application attempts to process the pathname as a regular file. | | 1 |
| 635 | CWE-671 | Lack of Administrator Control over Security | The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect the environment in which the product is being used. This introduces resultant weaknesses or prevents it from operating at a level of security that is desired by the administrator. | | 1 |
| 636 | CWE-683 | Function Call With Incorrect Order of Arguments | The product calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses. | | 1 |
| 637 | CWE-686 | Function Call With Incorrect Argument Type | The product calls a function, procedure, or routine, but the caller specifies an argument that is the wrong data type, which may lead to resultant weaknesses. | | 1 |
| 638 | CWE-689 | Permission Race Condition During Resource Copy | The product, while copying or cloning a resource, does not set the resource's permissions or access control until the copy is complete, leaving the resource exposed to other spheres while the copy is taking place. | CWE-362 | 1 |
| 639 | CWE-692 | Incomplete Denylist to Cross-Site Scripting | The product uses a denylist-based protection mechanism to defend against XSS attacks, but the denylist is incomplete, allowing XSS variants to succeed. | CWE-79 | 1 |
| 640 | CWE-758 | Reliance on Undefined, Unspecified, or Implementation-Defined Behavior | The product uses an API function, data structure, or other entity in a way that relies on properties that are not always guaranteed to hold for that entity. | | 1 |
| 641 | CWE-765 | Multiple Unlocks of a Critical Resource | The product unlocks a critical resource more times than intended, leading to an unexpected state in the system. | | 1 |
| 642 | CWE-828 | Signal Handler with Functionality that is not Asynchronous-Safe | The product defines a signal handler that contains code sequences that are not asynchronous-safe, i.e., the functionality is not reentrant, or it can be interrupted. | | 1 |
| 643 | CWE-839 | Numeric Range Comparison Without Minimum Check | The product checks a value to ensure that it is less than or equal to a maximum, but it does not also verify that the value is greater than or equal to the minimum. | CWE-118 | 1 |