Expand All | Collapse All
888 - Software Fault Pattern (SFP) Clusters
+CategoryCategorySFP Primary Cluster: API - (887)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API)
This category identifies Software Fault Patterns (SFPs) within the API cluster.
+CategoryCategorySFP Secondary Cluster: Use of an Improper API - (1001)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API)
This category identifies Software Fault Patterns (SFPs) within the Use of an Improper API cluster.
*Weakness BaseWeakness BaseBehavioral Change in New Version or Environment - (439)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 439 (Behavioral Change in New Version or Environment)
A's behavior or functionality changes with a new version of A, or a new environment, which is not known (or manageable) by B.Functional change
*Weakness VariantWeakness VariantCall to Non-ubiquitous API - (589)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 589 (Call to Non-ubiquitous API)
The software uses an API function that does not exist on all versions of the target platform. This could cause portability problems or inconsistencies that allow denial of service or other consequences.
*Weakness VariantWeakness VariantCall to Thread run() instead of start() - (572)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 572 (Call to Thread run() instead of start())
The program calls a thread's run() method instead of calling start(), which causes the code to run in the thread of the caller instead of the callee.
*Weakness BaseWeakness BaseDangerous Signal Handler not Disabled During Sensitive Operations - (432)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 432 (Dangerous Signal Handler not Disabled During Sensitive Operations)
The application uses a signal handler that shares state with other signal handlers, but it does not properly mask or prevent those signal handlers from being invoked while the original signal handler is still running.
*Weakness BaseWeakness BaseDirect Use of Unsafe JNI - (111)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 111 (Direct Use of Unsafe JNI)
When a Java application uses the Java Native Interface (JNI) to call code written in another programming language, it can expose the application to weaknesses in that code, even if those weaknesses cannot occur in Java.
*Weakness VariantWeakness VariantEJB Bad Practices: Use of AWT Swing - (575)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 575 (EJB Bad Practices: Use of AWT Swing)
The program violates the Enterprise JavaBeans (EJB) specification by using AWT/Swing.
*Weakness VariantWeakness VariantEJB Bad Practices: Use of Class Loader - (578)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 578 (EJB Bad Practices: Use of Class Loader)
The program violates the Enterprise JavaBeans (EJB) specification by using the class loader.
*Weakness VariantWeakness VariantEJB Bad Practices: Use of Java I/O - (576)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 576 (EJB Bad Practices: Use of Java I/O)
The program violates the Enterprise JavaBeans (EJB) specification by using the java.io package.
*Weakness VariantWeakness VariantEJB Bad Practices: Use of Sockets - (577)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 577 (EJB Bad Practices: Use of Sockets)
The program violates the Enterprise JavaBeans (EJB) specification by using sockets.
*Weakness VariantWeakness VariantEJB Bad Practices: Use of Synchronization Primitives - (574)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 574 (EJB Bad Practices: Use of Synchronization Primitives)
The program violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.
*Weakness BaseWeakness BaseExpected Behavior Violation - (440)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 440 (Expected Behavior Violation)
A feature, API, or function being used by a product behaves differently than the product expects.
*Weakness VariantWeakness VariantExplicit Call to Finalize() - (586)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 586 (Explicit Call to Finalize())
The software makes an explicit call to the finalize() method from outside the finalizer.
*Weakness ClassWeakness ClassImproper Following of Specification by Caller - (573)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 573 (Improper Following of Specification by Caller)
The software does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform.
*Weakness ClassWeakness ClassImproper Fulfillment of API Contract ('API Abuse') - (227)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 227 (Improper Fulfillment of API Contract ('API Abuse'))
The software uses an API in a manner contrary to its intended use.API Abuse
*Weakness BaseWeakness BaseIncorrect Provision of Specified Functionality - (684)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 684 (Incorrect Provision of Specified Functionality)
The code does not function according to its published specifications, potentially leading to incorrect usage.
*Weakness VariantWeakness VariantJ2EE Bad Practices: Direct Management of Connections - (245)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 245 (J2EE Bad Practices: Direct Management of Connections)
The J2EE application directly manages connections, instead of using the container's connection management facilities.
*Weakness VariantWeakness VariantJ2EE Bad Practices: Direct Use of Sockets - (246)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 246 (J2EE Bad Practices: Direct Use of Sockets)
The J2EE application directly uses sockets instead of using framework method calls.
*Weakness VariantWeakness VariantJ2EE Bad Practices: Direct Use of Threads - (383)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 383 (J2EE Bad Practices: Direct Use of Threads)
Thread management in a Web application is forbidden in some circumstances and is always highly error prone.
*Weakness VariantWeakness VariantJ2EE Bad Practices: Use of System.exit() - (382)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 382 (J2EE Bad Practices: Use of System.exit())
A J2EE application uses System.exit(), which also shuts down its container.
*Weakness VariantWeakness VariantReachable Assertion - (617)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 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.
*Weakness ClassWeakness ClassReliance on Undefined, Unspecified, or Implementation-Defined Behavior - (758)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior)
The software 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.
*Weakness VariantWeakness VariantSignal Handler Use of a Non-reentrant Function - (479)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 479 (Signal Handler Use of a Non-reentrant Function)
The program defines a signal handler that calls a non-reentrant function.
*Weakness BaseWeakness BaseUse of Function with Inconsistent Implementations - (474)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 474 (Use of Function with Inconsistent Implementations)
The code uses a function that has inconsistent implementations across operating systems and versions.
*Weakness BaseWeakness BaseUse of Inherently Dangerous Function - (242)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 242 (Use of Inherently Dangerous Function)
The program calls a function that can never be guaranteed to work safely.
*Weakness BaseWeakness BaseUse of Low-Level Functionality - (695)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 695 (Use of Low-Level Functionality)
The software uses low-level functionality that is explicitly prohibited by the framework or specification under which the software is supposed to operate.
*Weakness BaseWeakness BaseUse of Obsolete Functions - (477)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 477 (Use of Obsolete Functions)
The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.
*Weakness BaseWeakness BaseUse of Potentially Dangerous Function - (676)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 676 (Use of Potentially Dangerous Function)
The program invokes a potentially dangerous function that could introduce a vulnerability if it is used incorrectly, but the function can also be used safely.
*Weakness VariantWeakness VariantUse of getlogin() in Multithreaded Application - (558)
888 (Software Fault Pattern (SFP) Clusters) > 887 (SFP Primary Cluster: API) > 1001 (SFP Secondary Cluster: Use of an Improper API) > 558 (Use of getlogin() in Multithreaded Application)
The application uses the getlogin() function in a multithreaded context, potentially causing it to return incorrect values.
+CategoryCategorySFP Primary Cluster: Access Control - (899)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control)
This category identifies Software Fault Patterns (SFPs) within the Access Control cluster.
+CategoryCategorySFP Secondary Cluster: Access Management - (944)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 944 (SFP Secondary Cluster: Access Management)
This category identifies Software Fault Patterns (SFPs) within the Access Management cluster.
*Weakness ClassWeakness ClassImproper Access Control - (284)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 944 (SFP Secondary Cluster: Access Management) > 284 (Improper Access Control)
The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor.Authorization
*Weakness ClassWeakness ClassImproper Ownership Management - (282)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 944 (SFP Secondary Cluster: Access Management) > 282 (Improper Ownership Management)
The software assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.
*Weakness BaseWeakness BaseIncorrect Ownership Assignment - (708)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 944 (SFP Secondary Cluster: Access Management) > 708 (Incorrect Ownership Assignment)
The software assigns an owner to a resource, but the owner is outside of the intended control sphere.
*Weakness ClassWeakness ClassIncorrect User Management - (286)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 944 (SFP Secondary Cluster: Access Management) > 286 (Incorrect User Management)
The software does not properly manage a user within its environment.
*Weakness BaseWeakness BaseUnverified Ownership - (283)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 944 (SFP Secondary Cluster: Access Management) > 283 (Unverified Ownership)
The software does not properly verify that a critical resource is owned by the proper entity.
+CategoryCategorySFP Secondary Cluster: Insecure Resource Access - (945)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 945 (SFP Secondary Cluster: Insecure Resource Access)
This category identifies Software Fault Patterns (SFPs) within the Insecure Resource Access cluster.
*Weakness BaseWeakness BaseAuthorization Bypass Through User-Controlled Key - (639)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 945 (SFP Secondary Cluster: Insecure Resource Access) > 639 (Authorization Bypass Through User-Controlled Key)
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.Insecure Direct Object ReferenceHorizontal Authorization
*Weakness ClassWeakness ClassImproper Authorization - (285)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 945 (SFP Secondary Cluster: Insecure Resource Access) > 285 (Improper Authorization)
The software does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.AuthZ
*Weakness ClassWeakness ClassImproper Protection of Alternate Path - (424)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 945 (SFP Secondary Cluster: Insecure Resource Access) > 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.
*Weakness VariantWeakness VariantTrusting HTTP Permission Methods on the Server Side - (650)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 945 (SFP Secondary Cluster: Insecure Resource Access) > 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.
+CategoryCategorySFP Secondary Cluster: Insecure Resource Permissions - (946)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 946 (SFP Secondary Cluster: Insecure Resource Permissions)
This category identifies Software Fault Patterns (SFPs) within the Insecure Resource Permissions cluster.
*Weakness BaseWeakness BaseImproper Preservation of Permissions - (281)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 946 (SFP Secondary Cluster: Insecure Resource Permissions) > 281 (Improper Preservation of Permissions)
The software 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.
*Weakness VariantWeakness VariantIncorrect Default Permissions - (276)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 946 (SFP Secondary Cluster: Insecure Resource Permissions) > 276 (Incorrect Default Permissions)
The software, upon installation, sets incorrect permissions for an object that exposes it to an unintended actor.
*Weakness VariantWeakness VariantIncorrect Execution-Assigned Permissions - (279)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 946 (SFP Secondary Cluster: Insecure Resource Permissions) > 279 (Incorrect Execution-Assigned Permissions)
While it is executing, the software sets the permissions of an object in a way that violates the intended permissions that have been specified by the user.
*Weakness ClassWeakness ClassIncorrect Permission Assignment for Critical Resource - (732)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 946 (SFP Secondary Cluster: Insecure Resource Permissions) > 732 (Incorrect Permission Assignment for Critical Resource)
The software specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
*Weakness VariantWeakness VariantInsecure Inherited Permissions - (277)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 946 (SFP Secondary Cluster: Insecure Resource Permissions) > 277 (Insecure Inherited Permissions)
A product defines a set of insecure permissions that are inherited by objects that are created by the program.
*Weakness VariantWeakness VariantInsecure Preserved Inherited Permissions - (278)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 946 (SFP Secondary Cluster: Insecure Resource Permissions) > 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.
*Weakness VariantWeakness VariantUse of umask() with chmod-style Argument - (560)
888 (Software Fault Pattern (SFP) Clusters) > 899 (SFP Primary Cluster: Access Control) > 946 (SFP Secondary Cluster: Insecure Resource Permissions) > 560 (Use of umask() with chmod-style Argument)
The product calls umask() with an incorrect argument that is specified as if it is an argument to chmod().
+CategoryCategorySFP Primary Cluster: Authentication - (898)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication)
This category identifies Software Fault Patterns (SFPs) within the Authentication cluster.
+CategoryCategorySFP Secondary Cluster: Authentication Bypass - (947)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass)
This category identifies Software Fault Patterns (SFPs) within the Authentication Bypass cluster.
*Weakness ClassWeakness ClassAuthentication Bypass Issues - (592)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 592 (Authentication Bypass Issues)
The software does not properly perform authentication, allowing it to be bypassed through various methods.
*Weakness BaseWeakness BaseAuthentication Bypass Using an Alternate Path or Channel - (288)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 288 (Authentication Bypass Using an Alternate Path or Channel)
A product requires authentication, but the product has an alternate path or channel that does not require authentication.
*Weakness VariantWeakness VariantAuthentication Bypass by Alternate Name - (289)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 289 (Authentication Bypass by Alternate Name)
The software 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.
*Weakness BaseWeakness BaseAuthentication Bypass by Primary Weakness - (305)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 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.
*Weakness ClassWeakness ClassImproper Authentication - (287)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 287 (Improper Authentication)
When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct.authentificationAuthC
*Weakness BaseWeakness BaseIncorrect Implementation of Authentication Algorithm - (303)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 303 (Incorrect Implementation of Authentication Algorithm)
The requirements for the software dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.
*Weakness BaseWeakness BaseMissing Critical Step in Authentication - (304)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 304 (Missing Critical Step in Authentication)
The software implements an authentication technique, but it skips a step that weakens the technique.
*Weakness BaseWeakness BaseUse of Client-Side Authentication - (603)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 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.
*Weakness BaseWeakness BaseUse of Password System for Primary Authentication - (309)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 309 (Use of Password System for Primary Authentication)
The use of password systems as the primary means of authentication may be subject to several flaws or shortcomings, each reducing the effectiveness of the mechanism.
*Weakness BaseWeakness BaseUse of Single-factor Authentication - (308)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 947 (SFP Secondary Cluster: Authentication Bypass) > 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.
+CategoryCategorySFP Secondary Cluster: Digital Certificate - (948)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 948 (SFP Secondary Cluster: Digital Certificate)
This category identifies Software Fault Patterns (SFPs) within the Digital Certificate cluster.
*Weakness VariantWeakness VariantAuthentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created - (593)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 948 (SFP Secondary Cluster: Digital Certificate) > 593 (Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created)
The software modifies the SSL context after connection creation has begun.
*Weakness VariantWeakness VariantImproper Check for Certificate Revocation - (299)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 948 (SFP Secondary Cluster: Digital Certificate) > 299 (Improper Check for Certificate Revocation)
The software does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised.
*Weakness BaseWeakness BaseImproper Following of a Certificate's Chain of Trust - (296)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 948 (SFP Secondary Cluster: Digital Certificate) > 296 (Improper Following of a Certificate's Chain of Trust)
The software 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.
*Weakness VariantWeakness VariantImproper Validation of Certificate Expiration - (298)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 948 (SFP Secondary Cluster: Digital Certificate) > 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.
*Weakness VariantWeakness VariantImproper Validation of Certificate with Host Mismatch - (297)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 948 (SFP Secondary Cluster: Digital Certificate) > 297 (Improper Validation of Certificate with Host Mismatch)
The software communicates with a host that provides a certificate, but the software does not properly ensure that the certificate is actually associated with that host.
*Weakness VariantWeakness VariantMissing Validation of OpenSSL Certificate - (599)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 948 (SFP Secondary Cluster: Digital Certificate) > 599 (Missing Validation of OpenSSL Certificate)
The software 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.
+CategoryCategorySFP Secondary Cluster: Faulty Endpoint Authentication - (949)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication)
This category identifies Software Fault Patterns (SFPs) within the Faulty Endpoint Authentication cluster.
*Weakness VariantWeakness VariantAuthentication Bypass by Assumed-Immutable Data - (302)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication) > 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.
*Weakness BaseWeakness BaseIncorrect Behavior Order: Authorization Before Parsing and Canonicalization - (551)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication) > 551 (Incorrect Behavior Order: Authorization Before Parsing and Canonicalization)
If a web server does not fully parse requested URLs before it examines them for authorization, it may be possible for an attacker to bypass authorization protection.
*Weakness ClassWeakness ClassInsufficient Verification of Data Authenticity - (345)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication) > 345 (Insufficient Verification of Data Authenticity)
The software does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
*Weakness BaseWeakness BaseOrigin Validation Error - (346)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication) > 346 (Origin Validation Error)
The software does not properly verify that the source of data or communication is valid.
*Weakness BaseWeakness BaseReliance on Cookies without Validation and Integrity Checking - (565)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication) > 565 (Reliance on Cookies without Validation and Integrity Checking)
The application relies on the existence or values of cookies when performing security-critical operations, but it does not properly ensure that the setting is valid for the associated user.
*Weakness VariantWeakness VariantReliance on Reverse DNS Resolution for a Security-Critical Action - (350)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication) > 350 (Reliance on Reverse DNS Resolution for a Security-Critical Action)
The software 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.
*Weakness BaseWeakness BaseTrust of System Event Data - (360)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication) > 360 (Trust of System Event Data)
Security based on event locations are insecure and can be spoofed.
*Weakness VariantWeakness VariantUse of Non-Canonical URL Paths for Authorization Decisions - (647)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication) > 647 (Use of Non-Canonical URL Paths for Authorization Decisions)
The software 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.
*Weakness VariantWeakness VariantUsing Referer Field for Authentication - (293)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 949 (SFP Secondary Cluster: Faulty Endpoint Authentication) > 293 (Using Referer Field for Authentication)
The referer field in HTTP requests can be easily modified and, as such, is not a valid means of message integrity checking.referrer
+CategoryCategorySFP Secondary Cluster: Hardcoded Sensitive Data - (950)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 950 (SFP Secondary Cluster: Hardcoded Sensitive Data)
This category identifies Software Fault Patterns (SFPs) within the Hardcoded Sensitive Data cluster.
*Weakness VariantWeakness VariantEmpty Password in Configuration File - (258)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 950 (SFP Secondary Cluster: Hardcoded Sensitive Data) > 258 (Empty Password in Configuration File)
Using an empty string as a password is insecure.
*Weakness BaseWeakness BaseUse of Hard-coded Cryptographic Key - (321)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 950 (SFP Secondary Cluster: Hardcoded Sensitive Data) > 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.
*Weakness BaseWeakness BaseUse of Hard-coded Password - (259)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 950 (SFP Secondary Cluster: Hardcoded Sensitive Data) > 259 (Use of Hard-coded Password)
The software contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.
*Weakness VariantWeakness VariantUse of Hard-coded, Security-relevant Constants - (547)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 950 (SFP Secondary Cluster: Hardcoded Sensitive Data) > 547 (Use of Hard-coded, Security-relevant Constants)
The program 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.
+CategoryCategorySFP Secondary Cluster: Insecure Authentication Policy - (951)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 951 (SFP Secondary Cluster: Insecure Authentication Policy)
This category identifies Software Fault Patterns (SFPs) within the Insecure Authentication Policy cluster.
*Weakness VariantWeakness VariantASP.NET Misconfiguration: Use of Identity Impersonation - (556)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 951 (SFP Secondary Cluster: Insecure Authentication Policy) > 556 (ASP.NET Misconfiguration: Use of Identity Impersonation)
Configuring an ASP.NET application to run with impersonated credentials may give the application unnecessary privileges.
*Weakness BaseWeakness BaseInsufficient Session Expiration - (613)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 951 (SFP Secondary Cluster: Insecure Authentication Policy) > 613 (Insufficient 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."
*Weakness VariantWeakness VariantNot Using Password Aging - (262)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 951 (SFP Secondary Cluster: Insecure Authentication Policy) > 262 (Not Using Password Aging)
If no mechanism is in place for managing password aging, users will have no incentive to update passwords in a timely manner.
*Weakness BaseWeakness BaseOverly Restrictive Account Lockout Mechanism - (645)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 951 (SFP Secondary Cluster: Insecure Authentication Policy) > 645 (Overly Restrictive Account Lockout Mechanism)
The software contains an account lockout protection mechanism, but the mechanism is too restrictive and can be triggered too easily. This allows attackers to deny service to legitimate users by causing their accounts to be locked out.
*Weakness BaseWeakness BasePassword Aging with Long Expiration - (263)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 951 (SFP Secondary Cluster: Insecure Authentication Policy) > 263 (Password Aging with Long Expiration)
Allowing password aging to occur unchecked can result in the possibility of diminished password integrity.
*Weakness BaseWeakness BaseWeak Password Requirements - (521)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 951 (SFP Secondary Cluster: Insecure Authentication Policy) > 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.
+CategoryCategorySFP Secondary Cluster: Missing Authentication - (952)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 952 (SFP Secondary Cluster: Missing Authentication)
This category identifies Software Fault Patterns (SFPs) within the Missing Authentication cluster.
*Weakness VariantWeakness VariantMissing Authentication for Critical Function - (306)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 952 (SFP Secondary Cluster: Missing Authentication) > 306 (Missing Authentication for Critical Function)
The software does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
*Weakness VariantWeakness VariantUnverified Password Change - (620)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 952 (SFP Secondary Cluster: Missing Authentication) > 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.
+CategoryCategorySFP Secondary Cluster: Missing Endpoint Authentication - (953)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 953 (SFP Secondary Cluster: Missing Endpoint Authentication)
This category identifies Software Fault Patterns (SFPs) within the Missing Endpoint Authentication cluster.
*Weakness BaseWeakness BaseDirect Request ('Forced Browsing') - (425)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 953 (SFP Secondary Cluster: Missing Endpoint Authentication) > 425 (Direct Request ('Forced Browsing'))
The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.forced browsing
*Weakness VariantWeakness VariantUnprotected Windows Messaging Channel ('Shatter') - (422)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 953 (SFP Secondary Cluster: Missing Endpoint Authentication) > 422 (Unprotected Windows Messaging Channel ('Shatter'))
The software 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.
+CategoryCategorySFP Secondary Cluster: Multiple Binds to the Same Port - (954)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 954 (SFP Secondary Cluster: Multiple Binds to the Same Port)
This category identifies Software Fault Patterns (SFPs) within the Multiple Binds to the Same Port cluster.
*Weakness BaseWeakness BaseMultiple Binds to the Same Port - (605)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 954 (SFP Secondary Cluster: Multiple Binds to the Same Port) > 605 (Multiple Binds to the Same Port)
When multiple sockets are allowed to bind to the same port, other services on that port may be stolen or spoofed.
+CategoryCategorySFP Secondary Cluster: Unrestricted Authentication - (955)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 955 (SFP Secondary Cluster: Unrestricted Authentication)
This category identifies Software Fault Patterns (SFPs) within the Unrestricted Authentication cluster.
*Weakness BaseWeakness BaseImproper Restriction of Excessive Authentication Attempts - (307)
888 (Software Fault Pattern (SFP) Clusters) > 898 (SFP Primary Cluster: Authentication) > 955 (SFP Secondary Cluster: Unrestricted Authentication) > 307 (Improper Restriction of Excessive Authentication Attempts)
The software does not implement sufficient measures to prevent multiple failed authentication attempts within in a short time frame, making it more susceptible to brute force attacks.
+CategoryCategorySFP Primary Cluster: Channel - (902)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel)
This category identifies Software Fault Patterns (SFPs) within the Channel cluster.
+CategoryCategorySFP Secondary Cluster: Channel Attack - (956)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 956 (SFP Secondary Cluster: Channel Attack)
This category identifies Software Fault Patterns (SFPs) within the Channel Attack cluster.
*Weakness BaseWeakness BaseAuthentication Bypass by Capture-replay - (294)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 956 (SFP Secondary Cluster: Channel Attack) > 294 (Authentication Bypass by Capture-replay)
A capture-replay flaw exists when the design of the software 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).
*Weakness BaseWeakness BaseAuthentication Bypass by Spoofing - (290)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 956 (SFP Secondary Cluster: Channel Attack) > 290 (Authentication Bypass by Spoofing)
This attack-focused weakness is caused by improperly implemented authentication schemes that are subject to spoofing attacks.
*Weakness ClassWeakness ClassChannel Accessible by Non-Endpoint ('Man-in-the-Middle') - (300)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 956 (SFP Secondary Cluster: Channel Attack) > 300 (Channel Accessible by Non-Endpoint ('Man-in-the-Middle'))
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.
*Weakness BaseWeakness BaseRace Condition During Access to Alternate Channel - (421)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 956 (SFP Secondary Cluster: Channel Attack) > 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.
*Weakness VariantWeakness VariantReflection Attack in an Authentication Protocol - (301)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 956 (SFP Secondary Cluster: Channel Attack) > 301 (Reflection Attack in an Authentication Protocol)
Simple authentication protocols are subject to reflection attacks if a malicious user can use the target machine to impersonate a trusted user.
*Weakness ClassWeakness ClassUnintended Proxy or Intermediary ('Confused Deputy') - (441)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 956 (SFP Secondary Cluster: Channel Attack) > 441 (Unintended Proxy or Intermediary ('Confused Deputy'))
The software receives a request, message, or directive from an upstream component, but the software does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the software's control sphere. This causes the software 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.Confused Deputy
*Weakness BaseWeakness BaseUnprotected Alternate Channel - (420)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 956 (SFP Secondary Cluster: Channel Attack) > 420 (Unprotected Alternate Channel)
The software protects a primary channel, but it does not use the same level of protection for an alternate channel.
*Weakness BaseWeakness BaseUnprotected Primary Channel - (419)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 956 (SFP Secondary Cluster: Channel Attack) > 419 (Unprotected Primary Channel)
The software uses a primary channel for administration or restricted functionality, but it does not properly protect the channel.
+CategoryCategorySFP Secondary Cluster: Protocol Error - (957)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 957 (SFP Secondary Cluster: Protocol Error)
This category identifies Software Fault Patterns (SFPs) within the Protocol Error cluster.
*Weakness BaseWeakness BaseIncomplete Model of Endpoint Features - (437)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 957 (SFP Secondary Cluster: Protocol Error) > 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.
*Weakness ClassWeakness ClassInteraction Error - (435)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 957 (SFP Secondary Cluster: Protocol Error) > 435 (Interaction Error)
An interaction error occurs when two entities work correctly when running independently, but they interact in unexpected ways when they are run together.
*Weakness BaseWeakness BaseInterpretation Conflict - (436)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 957 (SFP Secondary Cluster: Protocol Error) > 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.
*Weakness BaseWeakness BaseMissing Support for Integrity Check - (353)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 957 (SFP Secondary Cluster: Protocol Error) > 353 (Missing Support for Integrity Check)
The software uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.
*Weakness ClassWeakness ClassSelection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade') - (757)
888 (Software Fault Pattern (SFP) Clusters) > 902 (SFP Primary Cluster: Channel) > 957 (SFP Secondary Cluster: Protocol Error) > 757 (Selection of Less-Secure Algorithm During Negotiation ('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.
+CategoryCategorySFP Primary Cluster: Cryptography - (903)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography)
This category identifies Software Fault Patterns (SFPs) within the Cryptography cluster.
+CategoryCategorySFP Secondary Cluster: Broken Cryptography - (958)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 958 (SFP Secondary Cluster: Broken Cryptography)
This category identifies Software Fault Patterns (SFPs) within the Broken Cryptography cluster.
*Weakness BaseWeakness BaseMissing Required Cryptographic Step - (325)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 958 (SFP Secondary Cluster: Broken Cryptography) > 325 (Missing Required Cryptographic Step)
The software does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by that algorithm.
*Weakness BaseWeakness BaseReversible One-Way Hash - (328)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 958 (SFP Secondary Cluster: Broken Cryptography) > 328 (Reversible One-Way Hash)
The product uses a hashing algorithm that produces a hash value that can be used to determine the original input, or to find an input that can produce the same hash, more efficiently than brute force techniques.
*Weakness BaseWeakness BaseUse of a Broken or Risky Cryptographic Algorithm - (327)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 958 (SFP Secondary Cluster: Broken Cryptography) > 327 (Use of a Broken or Risky Cryptographic Algorithm)
The use of a broken or risky cryptographic algorithm is an unnecessary risk that may result in the exposure of sensitive information.
*Weakness BaseWeakness BaseUse of a One-Way Hash with a Predictable Salt - (760)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 958 (SFP Secondary Cluster: Broken Cryptography) > 760 (Use of a One-Way Hash with a Predictable Salt)
The software uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the software uses a predictable salt as part of the input.
*Weakness BaseWeakness BaseUse of a One-Way Hash without a Salt - (759)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 958 (SFP Secondary Cluster: Broken Cryptography) > 759 (Use of a One-Way Hash without a Salt)
The software uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the software does not also use a salt as part of the input.
+CategoryCategorySFP Secondary Cluster: Weak Cryptography - (959)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 959 (SFP Secondary Cluster: Weak Cryptography)
This category identifies Software Fault Patterns (SFPs) within the Weak Cryptography cluster.
*Weakness BaseWeakness BaseImproper Verification of Cryptographic Signature - (347)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 959 (SFP Secondary Cluster: Weak Cryptography) > 347 (Improper Verification of Cryptographic Signature)
The software does not verify, or incorrectly verifies, the cryptographic signature for data.
*Weakness ClassWeakness ClassInadequate Encryption Strength - (326)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 959 (SFP Secondary Cluster: Weak Cryptography) > 326 (Inadequate Encryption Strength)
The software stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
*Weakness BaseWeakness BaseKey Exchange without Entity Authentication - (322)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 959 (SFP Secondary Cluster: Weak Cryptography) > 322 (Key Exchange without Entity Authentication)
The software performs a key exchange with an actor without verifying the identity of that actor.
*Weakness VariantWeakness VariantNot Using a Random IV with CBC Mode - (329)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 959 (SFP Secondary Cluster: Weak Cryptography) > 329 (Not Using a Random IV with CBC Mode)
Not using a random initialization Vector (IV) with Cipher Block Chaining (CBC) Mode causes algorithms to be susceptible to dictionary attacks.
*Weakness BaseWeakness BaseReusing a Nonce, Key Pair in Encryption - (323)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 959 (SFP Secondary Cluster: Weak Cryptography) > 323 (Reusing a Nonce, Key Pair in Encryption)
Nonces should be used for the present occasion and only once.
*Weakness BaseWeakness BaseUse of a Key Past its Expiration Date - (324)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 959 (SFP Secondary Cluster: Weak Cryptography) > 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.
*Weakness VariantWeakness VariantWeak Cryptography for Passwords - (261)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 959 (SFP Secondary Cluster: Weak Cryptography) > 261 (Weak Cryptography for Passwords)
Obscuring a password with a trivial encoding does not protect the password.
*Weakness BaseWeakness BaseWeak Password Recovery Mechanism for Forgotten Password - (640)
888 (Software Fault Pattern (SFP) Clusters) > 903 (SFP Primary Cluster: Cryptography) > 959 (SFP Secondary Cluster: Weak Cryptography) > 640 (Weak Password Recovery Mechanism for Forgotten Password)
The software contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
+CategoryCategorySFP Primary Cluster: Entry Points - (897)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points)
This category identifies Software Fault Patterns (SFPs) within the Entry Points cluster.
+CategoryCategorySFP Secondary Cluster: Unexpected Entry Points - (1002)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points)
This category identifies Software Fault Patterns (SFPs) within the Unexpected Entry Points cluster.
*Weakness VariantWeakness VariantArray Declared Public, Final, and Static - (582)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 582 (Array Declared Public, Final, and Static)
The program declares an array public, final, and static, which is not sufficient to prevent the array's contents from being modified.
*Weakness VariantWeakness VariantCritical Public Variable Without Final Modifier - (493)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 493 (Critical Public Variable Without Final Modifier)
The product has a critical public variable that is not final, which allows the variable to be modified to contain unexpected values.
*Weakness VariantWeakness VariantCritical Variable Declared Public - (766)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 766 (Critical Variable Declared Public)
The software declares a critical variable or field to be public when intended security policy requires it to be private.
*Weakness VariantWeakness VariantInformation Exposure Through Test Code - (531)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 531 (Information Exposure Through 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.
*Weakness BaseWeakness BaseLeftover Debug Code - (489)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 489 (Leftover Debug Code)
The application can be deployed with active debugging code that can create unintended entry points.
*Weakness VariantWeakness VariantPublic Static Field Not Marked Final - (500)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 500 (Public Static Field Not Marked Final)
An object contains a public static field that is not marked final, which might allow it to be modified in unexpected ways.
*Weakness VariantWeakness VariantPublic cloneable() Method Without Final ('Object Hijack') - (491)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 491 (Public cloneable() Method Without Final ('Object Hijack'))
A class has a cloneable() method that is not declared final, which allows an object to be created without calling the constructor. This can cause the object to be in an unexpected state.
*Weakness VariantWeakness VariantStruts: Non-private Field in ActionForm Class - (608)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 608 (Struts: Non-private Field in ActionForm Class)
An ActionForm class contains a field that has not been declared private, which can be accessed without using a setter or getter.
*Weakness VariantWeakness Variantclone() Method Without super.clone() - (580)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 580 (clone() Method Without super.clone())
The software contains a clone() method that does not call super.clone() to obtain the new object.
*Weakness VariantWeakness Variantfinalize() Method Declared Public - (583)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 583 (finalize() Method Declared Public)
The program violates secure coding principles for mobile code by declaring a finalize() method public.
*Weakness VariantWeakness Variantfinalize() Method Without super.finalize() - (568)
888 (Software Fault Pattern (SFP) Clusters) > 897 (SFP Primary Cluster: Entry Points) > 1002 (SFP Secondary Cluster: Unexpected Entry Points) > 568 (finalize() Method Without super.finalize())
The software contains a finalize() method that does not call super.finalize().
+CategoryCategorySFP Primary Cluster: Exception Management - (889)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management)
This category identifies Software Fault Patterns (SFPs) within the Exception Management cluster.
+CategoryCategorySFP Secondary Cluster: Ambiguous Exception Type - (960)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 960 (SFP Secondary Cluster: Ambiguous Exception Type)
This category identifies Software Fault Patterns (SFPs) within the Ambiguous Exception Type cluster.
*Weakness BaseWeakness BaseDeclaration of Catch for Generic Exception - (396)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 960 (SFP Secondary Cluster: Ambiguous Exception Type) > 396 (Declaration of Catch for Generic Exception)
Catching overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.
*Weakness BaseWeakness BaseDeclaration of Throws for Generic Exception - (397)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 960 (SFP Secondary Cluster: Ambiguous Exception Type) > 397 (Declaration of Throws for Generic Exception)
Throwing overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.
+CategoryCategorySFP Secondary Cluster: Incorrect Exception Behavior - (961)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 961 (SFP Secondary Cluster: Incorrect Exception Behavior)
This category identifies Software Fault Patterns (SFPs) within the Incorrect Exception Behavior cluster.
*Weakness ClassWeakness ClassImproper Check or Handling of Exceptional Conditions - (703)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 961 (SFP Secondary Cluster: Incorrect Exception Behavior) > 703 (Improper Check or Handling of Exceptional Conditions)
The software does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the software.
*Weakness VariantWeakness VariantImproper Cleanup on Thrown Exception - (460)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 961 (SFP Secondary Cluster: Incorrect Exception Behavior) > 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.
*Weakness BaseWeakness BaseMissing Report of Error Condition - (392)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 961 (SFP Secondary Cluster: Incorrect Exception Behavior) > 392 (Missing Report of Error Condition)
The software encounters an error but does not provide a status code or return value to indicate that an error has occurred.
*Weakness BaseWeakness BaseMissing Standardized Error Handling Mechanism - (544)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 961 (SFP Secondary Cluster: Incorrect Exception Behavior) > 544 (Missing Standardized Error Handling Mechanism)
The software does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses.
*Weakness BaseWeakness BaseNon-exit on Failed Initialization - (455)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 961 (SFP Secondary Cluster: Incorrect Exception Behavior) > 455 (Non-exit on Failed Initialization)
The software 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, which can cause the software to execute in a less secure fashion than intended by the administrator.
*Weakness ClassWeakness ClassNot Failing Securely ('Failing Open') - (636)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 961 (SFP Secondary Cluster: Incorrect Exception Behavior) > 636 (Not Failing Securely ('Failing Open'))
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.Failing Open
*Weakness BaseWeakness BaseReturn Inside Finally Block - (584)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 961 (SFP Secondary Cluster: Incorrect Exception Behavior) > 584 (Return Inside Finally Block)
The code has a return statement inside a finally block, which will cause any thrown exception in the try block to be discarded.
*Weakness BaseWeakness BaseReturn of Wrong Status Code - (393)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 961 (SFP Secondary Cluster: Incorrect Exception Behavior) > 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.
+CategoryCategorySFP Secondary Cluster: Unchecked Status Condition - (962)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition)
This category identifies Software Fault Patterns (SFPs) within the Unchecked Status Condition cluster.
*Weakness ClassWeakness ClassDetection of Error Condition Without Action - (390)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 390 (Detection of Error Condition Without Action)
The software detects a specific error, but takes no actions to handle the error.
*Weakness BaseWeakness BaseImproper Check for Dropped Privileges - (273)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 273 (Improper Check for Dropped Privileges)
The software attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded.
*Weakness ClassWeakness ClassImproper Check for Unusual or Exceptional Conditions - (754)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 754 (Improper Check for Unusual or Exceptional Conditions)
The software does not check or improperly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the software.
*Weakness ClassWeakness ClassImproper Handling of Exceptional Conditions - (755)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 755 (Improper Handling of Exceptional Conditions)
The software does not handle or incorrectly handles an exceptional condition.
*Weakness BaseWeakness BaseImproper Handling of Insufficient Permissions or Privileges - (280)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 280 (Improper Handling of Insufficient Permissions or Privileges )
The application 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 application in an invalid state.
*Weakness ClassWeakness ClassImproper Initialization - (665)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 665 (Improper Initialization)
The software does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
*Weakness BaseWeakness BaseIncomplete Internal State Distinction - (372)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 372 (Incomplete Internal State Distinction)
The software 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.
*Weakness BaseWeakness BaseIncorrect Check of Function Return Value - (253)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 253 (Incorrect Check of Function Return Value)
The software incorrectly checks a return value from a function, which prevents the software from detecting errors or exceptional conditions.
*Weakness VariantWeakness VariantMissing Default Case in Switch Statement - (478)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 478 (Missing Default Case in Switch Statement)
The code does not have a default case in a switch statement, which might lead to complex logical errors and resultant weaknesses.
*Weakness BaseWeakness BaseMissing Handler - (431)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 431 (Missing Handler)
A handler is not available or implemented.
*Weakness BaseWeakness BaseOmitted Break Statement in Switch - (484)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 484 (Omitted Break Statement in Switch)
The program omits a break statement within a switch or similar construct, causing code associated with multiple conditions to execute. This can cause problems when the programmer only intended to execute code associated with one condition.
*Weakness BaseWeakness BaseUncaught Exception - (248)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 248 (Uncaught Exception)
An exception is thrown from a function, but it is not caught.
*Weakness BaseWeakness BaseUncaught Exception in Servlet - (600)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 600 (Uncaught Exception in Servlet )
The Servlet does not catch all exceptions, which may reveal sensitive debugging information.Missing Catch Block
*Weakness BaseWeakness BaseUnchecked Error Condition - (391)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 391 (Unchecked Error Condition)
Ignoring exceptions and other error conditions may allow an attacker to induce unexpected behavior unnoticed.
*Weakness BaseWeakness BaseUnchecked Return Value - (252)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 252 (Unchecked Return Value)
The software does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions.
*Weakness BaseWeakness BaseUnexpected Status Code or Return Value - (394)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 394 (Unexpected Status Code or Return Value)
The software does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the software.
*Weakness BaseWeakness BaseUse of NullPointerException Catch to Detect NULL Pointer Dereference - (395)
888 (Software Fault Pattern (SFP) Clusters) > 889 (SFP Primary Cluster: Exception Management) > 962 (SFP Secondary Cluster: Unchecked Status Condition) > 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.
+CategoryCategorySFP Primary Cluster: Information Leak - (895)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak)
This category identifies Software Fault Patterns (SFPs) within the Information Leak cluster.
+CategoryCategorySFP Secondary Cluster: Exposed Data - (963)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data)
This category identifies Software Fault Patterns (SFPs) within the Exposed Data cluster.
*Weakness VariantWeakness VariantASP.NET Misconfiguration: Creating Debug Binary - (11)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 11 (ASP.NET Misconfiguration: Creating Debug Binary)
Debugging messages help attackers learn about the system and plan a form of attack.
*Weakness VariantWeakness VariantASP.NET Misconfiguration: Missing Custom Error Page - (12)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 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.
*Weakness VariantWeakness VariantASP.NET Misconfiguration: Password in Configuration File - (13)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 13 (ASP.NET Misconfiguration: Password in Configuration File)
Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource making them an easy target for attackers.
*Weakness VariantWeakness VariantAccess to Critical Private Variable via Public Method - (767)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 767 (Access to Critical Private Variable via Public Method)
The software defines a public method that reads or modifies a private variable.
*Weakness VariantWeakness VariantCleartext Storage in a File or on Disk - (313)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 313 (Cleartext Storage in a File or on Disk)
The application stores sensitive information in cleartext in a file, or on disk.
*Weakness VariantWeakness VariantCleartext Storage in the Registry - (314)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 314 (Cleartext Storage in the Registry)
The application stores sensitive information in cleartext in the registry.
*Weakness BaseWeakness BaseCleartext Storage of Sensitive Information - (312)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 312 (Cleartext Storage of Sensitive Information)
The application stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
*Weakness VariantWeakness VariantCleartext Storage of Sensitive Information in Executable - (318)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 318 (Cleartext Storage of Sensitive Information in Executable)
The application stores sensitive information in cleartext in an executable.
*Weakness VariantWeakness VariantCleartext Storage of Sensitive Information in GUI - (317)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 317 (Cleartext Storage of Sensitive Information in GUI)
The application stores sensitive information in cleartext within the GUI.
*Weakness VariantWeakness VariantCleartext Storage of Sensitive Information in Memory - (316)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 316 (Cleartext Storage of Sensitive Information in Memory)
The application stores sensitive information in cleartext in memory.
*Weakness VariantWeakness VariantCleartext Storage of Sensitive Information in a Cookie - (315)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 315 (Cleartext Storage of Sensitive Information in a Cookie)
The application stores sensitive information in cleartext in a cookie.
*Weakness BaseWeakness BaseCleartext Transmission of Sensitive Information - (319)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 319 (Cleartext Transmission of Sensitive Information)
The software transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
*Weakness VariantWeakness VariantCloneable Class Containing Sensitive Information - (498)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 498 (Cloneable Class Containing Sensitive Information)
The code contains a class with sensitive data, but the class is cloneable. The data can then be accessed by cloning the class.
*Weakness BaseWeakness BaseCompiler Removal of Code to Clear Buffers - (14)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 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."
*Weakness VariantWeakness VariantExposure of Access Control List Files to an Unauthorized Control Sphere - (529)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 529 (Exposure of Access Control List Files to an Unauthorized Control Sphere)
The product stores access control list files in a directory or other container that is accessible to actors outside of the intended control sphere.
*Weakness VariantWeakness VariantExposure of Backup File to an Unauthorized Control Sphere - (530)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 530 (Exposure of Backup File to an Unauthorized Control Sphere)
A backup file is stored in a directory that is accessible to actors outside of the intended control sphere.
*Weakness VariantWeakness VariantExposure of CVS Repository to an Unauthorized Control Sphere - (527)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 527 (Exposure of CVS Repository to an Unauthorized Control Sphere)
The product stores a CVS repository in a directory or other container that is accessible to actors outside of the intended control sphere.
*Weakness VariantWeakness VariantExposure of Core Dump File to an Unauthorized Control Sphere - (528)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 528 (Exposure of Core Dump File to an Unauthorized Control Sphere)
The product generates a core dump file in a directory that is accessible to actors outside of the intended control sphere.
*Weakness BaseWeakness BaseExposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak') - (403)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 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.File descriptor leak
*Weakness ClassWeakness ClassExposure of Resource to Wrong Sphere - (668)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 668 (Exposure of Resource to Wrong Sphere)
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
*Weakness VariantWeakness VariantExposure of System Data to an Unauthorized Control Sphere - (497)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 497 (Exposure of System Data to an Unauthorized Control Sphere)
Exposing system data or debugging information helps an adversary learn about the system and form an attack plan.
*Weakness ClassWeakness ClassExternal Control of Critical State Data - (642)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 642 (External Control of Critical State Data)
The software stores security-critical state information about its users, or the software itself, in a location that is accessible to unauthorized actors.
*Weakness BaseWeakness BaseFile and Directory Information Exposure - (538)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 538 (File and Directory Information Exposure)
The product stores sensitive information in files or directories that are accessible to actors outside of the intended control sphere.
*Weakness BaseWeakness BaseFiles or Directories Accessible to External Parties - (552)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 552 (Files or Directories Accessible to External Parties)
Files or directories are accessible in the environment that should not be.
*Weakness VariantWeakness VariantImproper Clearing of Heap Memory Before Release ('Heap Inspection') - (244)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 244 (Improper Clearing of Heap Memory Before Release ('Heap Inspection'))
Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory.
*Weakness BaseWeakness BaseImproper Cross-boundary Removal of Sensitive Data - (212)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 212 (Improper Cross-boundary Removal of Sensitive Data)
The software uses a resource that contains sensitive data, but it does not properly remove that data before it stores, transfers, or shares the resource with actors in another control sphere.
*Weakness BaseWeakness BaseImproper Output Neutralization for Logs - (117)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 117 (Improper Output Neutralization for Logs)
The software does not neutralize or incorrectly neutralizes output that is written to logs.
*Weakness ClassWeakness ClassIncorrect Resource Transfer Between Spheres - (669)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 669 (Incorrect Resource Transfer Between Spheres)
The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.
*Weakness ClassWeakness ClassInformation Exposure - (200)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 200 (Information Exposure)
An information exposure is the intentional or unintentional disclosure of information to an actor that is not explicitly authorized to have access to that information.Information LeakInformation Disclosure
*Weakness VariantWeakness VariantInformation Exposure Through Cleanup Log Files - (542)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 542 (Information Exposure Through Cleanup Log Files)
The application does not properly protect or delete a log file related to cleanup.
*Weakness VariantWeakness VariantInformation Exposure Through Comments - (615)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 615 (Information Exposure Through 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.
*Weakness VariantWeakness VariantInformation Exposure Through Debug Information - (215)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 215 (Information Exposure Through Debug Information)
The application contains debugging code that can expose sensitive information to untrusted parties.
*Weakness VariantWeakness VariantInformation Exposure Through Debug Log Files - (534)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 534 (Information Exposure Through Debug Log Files)
The application does not sufficiently restrict access to a log file that is used for debugging.
*Weakness VariantWeakness VariantInformation Exposure Through Directory Listing - (548)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 548 (Information Exposure Through Directory Listing)
A directory listing is inappropriately exposed, yielding potentially sensitive information to attackers.
*Weakness VariantWeakness VariantInformation Exposure Through Environmental Variables - (526)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 526 (Information Exposure Through Environmental Variables)
Environmental variables may contain sensitive information about a remote server.
*Weakness BaseWeakness BaseInformation Exposure Through Externally-generated Error Message - (211)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 211 (Information Exposure Through Externally-generated Error Message)
The software performs an operation that triggers an external diagnostic or error message that is not directly generated by the software, such as an error generated by the programming language interpreter that the software uses. The error can contain sensitive system information.
*Weakness VariantWeakness VariantInformation Exposure Through Include Source Code - (541)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 541 (Information Exposure Through Include Source Code)
If an include file source is accessible, the file can contain usernames and passwords, as well as sensitive information pertaining to the application and system.
*Weakness VariantWeakness VariantInformation Exposure Through Indexing of Private Data - (612)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 612 (Information Exposure Through Indexing of Private Data)
The product performs an indexing routine against private documents, but does not sufficiently verify that the actors who can access the index also have the privileges to access the private documents.
*Weakness VariantWeakness VariantInformation Exposure Through Java Runtime Error Message - (537)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 537 (Information Exposure Through Java Runtime Error Message)
In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system.
*Weakness VariantWeakness VariantInformation Exposure Through Log Files - (532)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 532 (Information Exposure Through 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.
*Weakness VariantWeakness VariantInformation Exposure Through Persistent Cookies - (539)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 539 (Information Exposure Through Persistent Cookies)
Persistent cookies are cookies that are stored on the browser's hard drive. This can cause security and privacy issues depending on the information stored in the cookie and how it is accessed.
*Weakness VariantWeakness VariantInformation Exposure Through Process Environment - (214)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 214 (Information Exposure Through Process Environment)
A process is invoked with sensitive arguments, environment variables, or other elements that can be seen by other processes on the operating system.
*Weakness VariantWeakness VariantInformation Exposure Through Query Strings in GET Request - (598)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 598 (Information Exposure Through Query Strings in GET Request)
The web application uses the GET method to process requests that contain sensitive information, which can expose that information through the browser's history, Referers, web logs, and other sources.
*Weakness BaseWeakness BaseInformation Exposure Through Self-generated Error Message - (210)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 210 (Information Exposure Through Self-generated Error Message)
The software identifies an error condition and creates its own diagnostic or error messages that contain sensitive information.
*Weakness VariantWeakness VariantInformation Exposure Through Sent Data - (201)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 201 (Information Exposure Through Sent Data)
The accidental exposure of sensitive information through sent data refers to the transmission of data which are either sensitive in and of itself or useful in the further exploitation of the system through standard data channels.
*Weakness VariantWeakness VariantInformation Exposure Through Server Error Message - (550)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 550 (Information Exposure Through Server Error Message)
Certain conditions, such as network failure, will cause a server error message to be displayed.
*Weakness VariantWeakness VariantInformation Exposure Through Server Log Files - (533)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 533 (Information Exposure Through Server Log Files)
A server.log file was found. This can give information on whatever application left the file. Usually this can give full path names and system information, and sometimes usernames and passwords.
*Weakness VariantWeakness VariantInformation Exposure Through Servlet Runtime Error Message - (536)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 536 (Information Exposure Through Servlet Runtime Error Message)
A servlet error message indicates that there exists an unhandled exception in your web application code and may provide useful information to an attacker.
*Weakness VariantWeakness VariantInformation Exposure Through Shell Error Message - (535)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 535 (Information Exposure Through Shell Error Message)
A command shell error message indicates that there exists an unhandled exception in the web application code. In many cases, an attacker can leverage the conditions that cause these errors in order to gain unauthorized access to the system.
*Weakness VariantWeakness VariantInformation Exposure Through Source Code - (540)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 540 (Information Exposure Through Source Code)
Source code on a web server often contains sensitive information and should generally not be accessible to users.
*Weakness BaseWeakness BaseInformation Exposure Through an Error Message - (209)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 209 (Information Exposure Through an Error Message)
The software generates an error message that includes sensitive information about its environment, users, or associated data.
*Weakness BaseWeakness BaseInsufficiently Protected Credentials - (522)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 522 (Insufficiently Protected Credentials)
This weakness occurs when the application transmits or stores authentication credentials and uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
*Weakness BaseWeakness BaseIntentional Information Exposure - (213)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 213 (Intentional Information Exposure)
A product's design or configuration explicitly requires the publication of information that could be regarded as sensitive by an administrator.
*Weakness VariantWeakness VariantJ2EE Misconfiguration: Data Transmission Without Encryption - (5)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 5 (J2EE Misconfiguration: Data Transmission Without Encryption)
Information sent over a network can be compromised while in transit. An attacker may be able to read/modify the contents if the data are sent in plaintext or are weakly encrypted.
*Weakness VariantWeakness VariantJ2EE Misconfiguration: Entity Bean Declared Remote - (8)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 8 (J2EE Misconfiguration: Entity Bean Declared Remote)
When an application exposes a remote interface for an entity bean, it might also expose methods that get or set the bean's data. These methods could be leveraged to read sensitive information, or to change data in ways that violate the application's expectations, potentially leading to other vulnerabilities.
*Weakness VariantWeakness VariantJ2EE Misconfiguration: Missing Custom Error Page - (7)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 7 (J2EE Misconfiguration: Missing Custom Error Page)
The default error page of a web application should not display sensitive information about the software system.
*Weakness VariantWeakness VariantJ2EE Misconfiguration: Plaintext Password in Configuration File - (555)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 555 (J2EE Misconfiguration: Plaintext Password in Configuration File)
The J2EE application stores a plaintext password in a configuration file.
*Weakness ClassWeakness ClassMissing Custom Error Page - (756)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 756 (Missing Custom Error Page)
The software does not return custom error pages to the user, possibly exposing sensitive information.
*Weakness BaseWeakness BaseMissing Encryption of Sensitive Data - (311)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 311 (Missing Encryption of Sensitive Data)
The software does not encrypt sensitive or critical information before storage or transmission.
*Weakness BaseWeakness BasePassing Mutable Objects to an Untrusted Method - (374)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 374 (Passing Mutable Objects to an Untrusted Method)
The program sends non-cloned mutable data as an argument to a method or function.
*Weakness VariantWeakness VariantPassword in Configuration File - (260)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 260 (Password in Configuration File)
The software stores a password in a configuration file that might be accessible to actors who do not know the password.
*Weakness VariantWeakness VariantPlaintext Storage of a Password - (256)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 256 (Plaintext Storage of a Password)
Storing a password in plaintext may result in a system compromise.
*Weakness VariantWeakness VariantPrivate Array-Typed Field Returned From A Public Method - (495)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 495 (Private Array-Typed Field Returned From A Public Method)
The product has a method that is declared public, but returns a reference to a private array, which could then be modified in unexpected ways.
*Weakness VariantWeakness VariantPublic Static Final Field References Mutable Object - (607)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 607 (Public Static Final Field References Mutable Object)
A public or protected static final field references a mutable object, which allows the object to be changed by malicious code, or accidentally from another package.
*Weakness BaseWeakness BaseReturning a Mutable Object to an Untrusted Caller - (375)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 375 (Returning a Mutable Object to an Untrusted Caller)
Sending non-cloned mutable data as a return value may result in that data being altered or deleted by the calling function.
*Weakness VariantWeakness VariantSensitive Data Storage in Improperly Locked Memory - (591)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 591 (Sensitive Data Storage in Improperly Locked Memory)
The application 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.
*Weakness VariantWeakness VariantSensitive Data Under FTP Root - (220)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 220 (Sensitive Data Under FTP Root)
The application stores sensitive data under the FTP document root with insufficient access control, which might make it accessible to untrusted parties.
*Weakness VariantWeakness VariantSensitive Data Under Web Root - (219)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 219 (Sensitive Data Under Web Root)
The application stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.
*Weakness BaseWeakness BaseSensitive Information Uncleared Before Release - (226)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 226 (Sensitive Information Uncleared Before Release)
The software does not fully clear previously used information in a data structure, file, or other resource, before making that resource available to a party in another control sphere.
*Weakness VariantWeakness VariantSerializable Class Containing Sensitive Data - (499)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 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.
*Weakness BaseWeakness BaseStoring Passwords in a Recoverable Format - (257)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 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.
*Weakness VariantWeakness VariantSuspicious Comment - (546)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 546 (Suspicious Comment)
The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses.
*Weakness ClassWeakness ClassTransmission of Private Resources into a New Sphere ('Resource Leak') - (402)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 402 (Transmission of Private Resources into a New Sphere ('Resource Leak'))
The software makes resources available to untrusted parties when those resources are only intended to be accessed by the software.Resource Leak
*Weakness BaseWeakness BaseTrust Boundary Violation - (501)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 501 (Trust Boundary Violation)
The product mixes trusted and untrusted data in the same data structure or structured message.
*Weakness VariantWeakness VariantUnparsed Raw Web Content Delivery - (433)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 433 (Unparsed Raw Web Content Delivery)
The software stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.
*Weakness VariantWeakness VariantUnprotected Transport of Credentials - (523)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 963 (SFP Secondary Cluster: Exposed Data) > 523 (Unprotected Transport of Credentials)
Login pages not using adequate measures to protect the user name and password while they are in transit from the client to the server.
+CategoryCategorySFP Secondary Cluster: Exposure Temporary File - (964)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 964 (SFP Secondary Cluster: Exposure Temporary File)
This category identifies Software Fault Patterns (SFPs) within the Exposure Temporary File cluster.
*Weakness BaseWeakness BaseCreation of Temporary File With Insecure Permissions - (378)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 964 (SFP Secondary Cluster: Exposure Temporary File) > 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.
*Weakness BaseWeakness BaseCreation of Temporary File in Directory with Incorrect Permissions - (379)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 964 (SFP Secondary Cluster: Exposure Temporary File) > 379 (Creation of Temporary File in Directory with Incorrect Permissions)
The software creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.
*Weakness BaseWeakness BaseInsecure Temporary File - (377)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 964 (SFP Secondary Cluster: Exposure Temporary File) > 377 (Insecure Temporary File)
Creating and using insecure temporary files can leave application and system data vulnerable to attack.
+CategoryCategorySFP Secondary Cluster: Insecure Session Management - (965)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 965 (SFP Secondary Cluster: Insecure Session Management)
This category identifies Software Fault Patterns (SFPs) within the Insecure Session Management cluster.
*Weakness VariantWeakness VariantExposure of Data Element to Wrong Session - (488)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 965 (SFP Secondary Cluster: Insecure Session Management) > 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.
*Weakness VariantWeakness VariantInformation Exposure Through Caching - (524)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 965 (SFP Secondary Cluster: Insecure Session Management) > 524 (Information Exposure Through Caching)
The application uses a cache to maintain a pool of objects, threads, connections, pages, or passwords to minimize the time it takes to access them or the resources to which they connect. If implemented improperly, these caches can allow access to unauthorized information or cause a denial of service vulnerability.
*Weakness VariantWeakness VariantJ2EE Misconfiguration: Insufficient Session-ID Length - (6)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 965 (SFP Secondary Cluster: Insecure Session Management) > 6 (J2EE Misconfiguration: Insufficient Session-ID Length)
The J2EE application is configured to use an insufficient session ID length.
+CategoryCategorySFP Secondary Cluster: Other Exposures - (966)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 966 (SFP Secondary Cluster: Other Exposures)
This category identifies Software Fault Patterns (SFPs) within the Other Exposures cluster.
*Weakness VariantWeakness VariantInformation Exposure Through Browser Caching - (525)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 966 (SFP Secondary Cluster: Other Exposures) > 525 (Information Exposure Through Browser Caching)
For each web page, the application should have an appropriate caching policy specifying the extent to which the page and its form fields should be cached.
*Weakness VariantWeakness VariantInformation Exposure Through WSDL File - (651)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 966 (SFP Secondary Cluster: Other Exposures) > 651 (Information Exposure Through WSDL File)
The Web services architecture may require exposing a WSDL file that contains information on the publicly accessible services and how callers of these services should interact with them (e.g. what parameters they expect and what types they return).
*Weakness BaseWeakness BaseInsecure Default Variable Initialization - (453)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 966 (SFP Secondary Cluster: Other Exposures) > 453 (Insecure Default Variable Initialization)
The software, by default, initializes an internal variable with an insecure or less secure value than is possible.
*Weakness ClassWeakness ClassInsufficient Encapsulation - (485)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 966 (SFP Secondary Cluster: Other Exposures) > 485 (Insufficient Encapsulation)
The product does not sufficiently encapsulate critical data or functionality.
*Weakness VariantWeakness VariantReliance on Package-level Scope - (487)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 966 (SFP Secondary Cluster: Other Exposures) > 487 (Reliance on Package-level Scope)
Java packages are not inherently closed; therefore, relying on them for code security is not a good practice.
*Weakness VariantWeakness VariantSensitive Cookie in HTTPS Session Without 'Secure' Attribute - (614)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 966 (SFP Secondary Cluster: Other Exposures) > 614 (Sensitive Cookie in HTTPS Session 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.
*Weakness VariantWeakness VariantUse of Inner Class Containing Sensitive Data - (492)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 966 (SFP Secondary Cluster: Other Exposures) > 492 (Use of Inner Class Containing Sensitive Data)
Inner classes are translated into classes that are accessible at package scope and may expose code that the programmer intended to keep private to attackers.
+CategoryCategorySFP Secondary Cluster: State Disclosure - (967)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 967 (SFP Secondary Cluster: State Disclosure)
This category identifies Software Fault Patterns (SFPs) within the State Disclosure cluster.
*Weakness VariantWeakness VariantExposure of Sensitive Data Through Data Queries - (202)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 967 (SFP Secondary Cluster: State Disclosure) > 202 (Exposure of Sensitive Data Through Data Queries)
When trying to keep information confidential, an attacker can often infer some of the information by using statistics.
*Weakness BaseWeakness BaseInformation Exposure Through Behavioral Discrepancy - (205)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 967 (SFP Secondary Cluster: State Disclosure) > 205 (Information Exposure Through Behavioral Discrepancy)
The product's actions indicate important differences based on (1) the internal state of the product or (2) differences from other products in the same class.
*Weakness ClassWeakness ClassInformation Exposure Through Discrepancy - (203)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 967 (SFP Secondary Cluster: State Disclosure) > 203 (Information Exposure Through Discrepancy)
The product behaves differently or sends different responses in a way that exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.
*Weakness BaseWeakness BaseInformation Exposure Through Timing Discrepancy - (208)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 967 (SFP Secondary Cluster: State Disclosure) > 208 (Information Exposure Through 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.
*Weakness VariantWeakness VariantInformation Exposure Through an External Behavioral Inconsistency - (207)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 967 (SFP Secondary Cluster: State Disclosure) > 207 (Information Exposure Through an External Behavioral Inconsistency)
The product behaves differently than other products like it, in a way that is observable to an attacker and exposes security-relevant information about which product is being used.
*Weakness VariantWeakness VariantInformation Exposure of Internal State Through Behavioral Inconsistency - (206)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 967 (SFP Secondary Cluster: State Disclosure) > 206 (Information Exposure of Internal State Through Behavioral Inconsistency)
Two separate operations in a product cause the product to behave differently in a way that is observable to an attacker and reveals security-relevant information about the internal state of the product, such as whether a particular operation was successful or not.
*Weakness BaseWeakness BaseResponse Discrepancy Information Exposure - (204)
888 (Software Fault Pattern (SFP) Clusters) > 895 (SFP Primary Cluster: Information Leak) > 967 (SFP Secondary Cluster: State Disclosure) > 204 (Response Discrepancy Information Exposure)
The software provides different responses to incoming requests in a way that allows an actor to determine system state information that is outside of that actor's control sphere.
+CategoryCategorySFP Primary Cluster: Malware - (904)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware)
This category identifies Software Fault Patterns (SFPs) within the Malware cluster.
*Weakness ClassWeakness ClassEmbedded Malicious Code - (506)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 506 (Embedded Malicious Code)
The application contains code that appears to be malicious in nature.
*Weakness VariantWeakness VariantImproper Handling of Windows ::DATA Alternate Data Stream - (69)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 69 (Improper Handling of Windows ::DATA Alternate Data Stream)
The software does not properly prevent access to, or detect usage of, alternate data streams (ADS).
*Weakness BaseWeakness BaseLogic/Time Bomb - (511)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 511 (Logic/Time Bomb)
The software contains code that is designed to disrupt the legitimate operation of the software (or its environment) when a certain time passes, or when a certain logical condition is met.
*Weakness BaseWeakness BaseNon-Replicating Malicious Code - (508)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 508 (Non-Replicating Malicious Code)
Non-replicating malicious code only resides on the target system or software that is attacked; it does not attempt to spread to other systems.
*Weakness BaseWeakness BaseReplicating Malicious Code (Virus or Worm) - (509)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 509 (Replicating Malicious Code (Virus or Worm))
Replicating malicious code, including viruses and worms, will attempt to attack other systems once it has successfully compromised the target system or software.
+CategoryCategorySFP Secondary Cluster: Covert Channel - (968)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 968 (SFP Secondary Cluster: Covert Channel)
This category identifies Software Fault Patterns (SFPs) within the Covert Channel cluster.
*Weakness ClassWeakness ClassCovert Channel - (514)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 968 (SFP Secondary Cluster: Covert Channel) > 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.
*Weakness BaseWeakness BaseCovert Storage Channel - (515)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 968 (SFP Secondary Cluster: Covert Channel) > 515 (Covert Storage Channel)
A covert storage channel transfers information through the setting of bits by one program and the reading of those bits by another. What distinguishes this case from that of ordinary operation is that the bits are used to convey encoded information.
*Weakness BaseWeakness BaseCovert Timing Channel - (385)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 968 (SFP Secondary Cluster: Covert Channel) > 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.
*Weakness BaseWeakness BaseSpyware - (512)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 512 (Spyware)
The software collects personally identifiable information about a human user or the user's activities, but the software accesses this information using other resources besides itself, and it does not require that user's explicit approval or direct input into the software.
*Weakness BaseWeakness BaseTrapdoor - (510)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 510 (Trapdoor)
A trapdoor is a hidden piece of code that responds to a special input, allowing its user access to resources without passing through the normal security enforcement mechanism.
*Weakness BaseWeakness BaseTrojan Horse - (507)
888 (Software Fault Pattern (SFP) Clusters) > 904 (SFP Primary Cluster: Malware) > 507 (Trojan Horse)
The software appears to contain benign or useful functionality, but it also contains code that is hidden from normal operation that violates the intended security policy of the user or the system administrator.
+CategoryCategorySFP Primary Cluster: Memory Access - (890)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access)
This category identifies Software Fault Patterns (SFPs) within the Memory Access cluster.
+CategoryCategorySFP Secondary Cluster: Faulty Buffer Access - (970)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access)
This category identifies Software Fault Patterns (SFPs) within the Faulty Buffer Access cluster.
*Weakness BaseWeakness BaseBuffer Copy without Checking Size of Input ('Classic Buffer Overflow') - (120)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 120 (Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'))
The program 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.buffer overrunUnbounded Transfer
*Weakness VariantWeakness VariantBuffer Over-read - (126)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 126 (Buffer Over-read)
The software reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.
*Weakness VariantWeakness VariantBuffer Under-read - (127)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 127 (Buffer Under-read)
The software reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations prior to the targeted buffer.
*Weakness BaseWeakness BaseBuffer Underwrite ('Buffer Underflow') - (124)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 124 (Buffer Underwrite ('Buffer Underflow'))
The software writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer. buffer underrun
*Weakness VariantWeakness VariantHeap-based Buffer Overflow - (122)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 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().
*Weakness ClassWeakness ClassImproper Access of Indexable Resource ('Range Error') - (118)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 118 (Improper Access of Indexable Resource ('Range Error'))
The software 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.
*Weakness ClassWeakness ClassImproper Restriction of Operations within the Bounds of a Memory Buffer - (119)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)
The software 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.Memory Corruption
*Weakness BaseWeakness BaseImproper Validation of Array Index - (129)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 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. out-of-bounds array indexindex-out-of-rangearray index underflow
*Weakness BaseWeakness BaseOut-of-bounds Read - (125)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 125 (Out-of-bounds Read)
The software reads data past the end, or before the beginning, of the intended buffer.
*Weakness VariantWeakness VariantStack-based Buffer Overflow - (121)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 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).Stack Overflow
*Weakness BaseWeakness BaseWrite-what-where Condition - (123)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 970 (SFP Secondary Cluster: Faulty Buffer Access) > 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.
+CategoryCategorySFP Secondary Cluster: Faulty Pointer Use - (971)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 971 (SFP Secondary Cluster: Faulty Pointer Use)
This category identifies Software Fault Patterns (SFPs) within the Faulty Pointer Use cluster.
*Weakness VariantWeakness VariantAttempt to Access Child of a Non-structure Pointer - (588)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 971 (SFP Secondary Cluster: Faulty Pointer Use) > 588 (Attempt to Access Child of a Non-structure Pointer)
Casting a non-structure type to a structure type and accessing a field can lead to memory access errors or data corruption.
*Weakness BaseWeakness BaseNULL Pointer Dereference - (476)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 971 (SFP Secondary Cluster: Faulty Pointer Use) > 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.
*Weakness BaseWeakness BaseUse of Pointer Subtraction to Determine Size - (469)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 971 (SFP Secondary Cluster: Faulty Pointer Use) > 469 (Use of Pointer Subtraction to Determine Size)
The application subtracts one pointer from another in order to determine size, but this calculation can be incorrect if the pointers do not exist in the same memory chunk.
+CategoryCategorySFP Secondary Cluster: Faulty String Expansion - (972)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 972 (SFP Secondary Cluster: Faulty String Expansion)
This category identifies Software Fault Patterns (SFPs) within the Faulty String Expansion cluster.
*Weakness VariantWeakness VariantUse of Path Manipulation Function without Maximum-sized Buffer - (785)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 972 (SFP Secondary Cluster: Faulty String Expansion) > 785 (Use of Path Manipulation Function without Maximum-sized Buffer)
The software invokes a function for normalizing paths or file names, but it provides an output buffer that is smaller than the maximum possible size, such as PATH_MAX.
+CategoryCategorySFP Secondary Cluster: Improper NULL Termination - (973)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 973 (SFP Secondary Cluster: Improper NULL Termination)
This category identifies Software Fault Patterns (SFPs) within the Improper NULL Termination cluster.
*Weakness BaseWeakness BaseImproper Null Termination - (170)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 973 (SFP Secondary Cluster: Improper NULL Termination) > 170 (Improper Null Termination)
The software does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator.
+CategoryCategorySFP Secondary Cluster: Incorrect Buffer Length Computation - (974)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 974 (SFP Secondary Cluster: Incorrect Buffer Length Computation)
This category identifies Software Fault Patterns (SFPs) within the Incorrect Buffer Length Computation cluster.
*Weakness BaseWeakness BaseIncorrect Calculation of Buffer Size - (131)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 974 (SFP Secondary Cluster: Incorrect Buffer Length Computation) > 131 (Incorrect Calculation of Buffer Size)
The software does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.
*Weakness BaseWeakness BaseIncorrect Calculation of Multi-Byte String Length - (135)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 974 (SFP Secondary Cluster: Incorrect Buffer Length Computation) > 135 (Incorrect Calculation of Multi-Byte String Length)
The software does not correctly calculate the length of strings that can contain wide or multi-byte characters.
*Weakness VariantWeakness VariantUse of sizeof() on a Pointer Type - (467)
888 (Software Fault Pattern (SFP) Clusters) > 890 (SFP Primary Cluster: Memory Access) > 974 (SFP Secondary Cluster: Incorrect Buffer Length Computation) > 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.
+CategoryCategorySFP Primary Cluster: Memory Management - (891)
888 (Software Fault Pattern (SFP) Clusters) > 891 (SFP Primary Cluster: Memory Management)
This category identifies Software Fault Patterns (SFPs) within the Memory Management cluster.
+CategoryCategorySFP Secondary Cluster: Faulty Memory Release - (969)
888 (Software Fault Pattern (SFP) Clusters) > 891 (SFP Primary Cluster: Memory Management) > 969 (SFP Secondary Cluster: Faulty Memory Release)
This category identifies Software Fault Patterns (SFPs) within the Faulty Memory Release cluster.
*Weakness VariantWeakness VariantDouble Free - (415)
888 (Software Fault Pattern (SFP) Clusters) > 891 (SFP Primary Cluster: Memory Management) > 969 (SFP Secondary Cluster: Faulty Memory Release) > 415 (Double Free)
The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.Double-free
*Weakness VariantWeakness VariantFree of Memory not on the Heap - (590)
888 (Software Fault Pattern (SFP) Clusters) > 891 (SFP Primary Cluster: Memory Management) > 969 (SFP Secondary Cluster: Faulty Memory Release) > 590 (Free of Memory not on the Heap)
The application calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().
*Weakness VariantWeakness VariantFree of Pointer not at Start of Buffer - (761)
888 (Software Fault Pattern (SFP) Clusters) > 891 (SFP Primary Cluster: Memory Management) > 969 (SFP Secondary Cluster: Faulty Memory Release) > 761 (Free of Pointer not at Start of Buffer)
The application calls free() on a pointer to a memory resource that was allocated on the heap, but the pointer is not at the start of the buffer.
*Weakness VariantWeakness VariantMismatched Memory Management Routines - (762)
888 (Software Fault Pattern (SFP) Clusters) > 891 (SFP Primary Cluster: Memory Management) > 969 (SFP Secondary Cluster: Faulty Memory Release) > 762 (Mismatched Memory Management Routines)
The application 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.
*Weakness BaseWeakness BaseRelease of Invalid Pointer or Reference - (763)
888 (Software Fault Pattern (SFP) Clusters) > 891 (SFP Primary Cluster: Memory Management) > 969 (SFP Secondary Cluster: Faulty Memory Release) > 763 (Release of Invalid Pointer or Reference)
The application attempts to return a memory resource to the system, but calls the wrong release function or calls the appropriate release function incorrectly.
+CategoryCategorySFP Primary Cluster: Other - (907)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other)
This category identifies Software Fault Patterns (SFPs) within the Other cluster.
+CategoryCategorySFP Secondary Cluster: Architecture - (975)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture)
This category identifies Software Fault Patterns (SFPs) within the Architecture cluster.
*Weakness BaseWeakness BaseClient-Side Enforcement of Server-Side Security - (602)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 602 (Client-Side Enforcement of Server-Side Security)
The software is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.
*Weakness BaseWeakness BaseExposed Dangerous Method or Function - (749)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 749 (Exposed Dangerous Method or Function)
The software 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.
*Weakness ClassWeakness ClassExposure of Private Information ('Privacy Violation') - (359)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 359 (Exposure of Private Information ('Privacy Violation'))
The software does not properly prevent private data (such as credit card numbers) from being accessed by actors who either (1) are not explicitly authorized to access the data or (2) do not have the implicit consent of the people to which the data is related. Privacy leakPrivacy leakage
*Weakness ClassWeakness ClassLack of Administrator Control over Security - (671)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 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.
*Weakness ClassWeakness ClassProtection Mechanism Failure - (693)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 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.
*Weakness BaseWeakness BaseReliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking - (649)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 649 (Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking)
The software uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the software does not use integrity checks to detect if those inputs have been modified.
*Weakness BaseWeakness BaseReliance on Security Through Obscurity - (656)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 656 (Reliance on Security Through Obscurity)
The software 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.Never Assuming your secrets are safe
*Weakness BaseWeakness BaseReliance on a Single Factor in a Security Decision - (654)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 654 (Reliance on a Single Factor in a Security Decision)
A protection mechanism relies exclusively, or to a large extent, on the evaluation of a single condition or the integrity of a single object or entity in order to make a decision about granting access to restricted resources or functionality.Separation of Privilege
*Weakness ClassWeakness ClassUnnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism') - (637)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 637 (Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism'))
The software uses a more complex mechanism than necessary, which could lead to resultant weaknesses when the mechanism is not correctly understood, modeled, configured, implemented, or used.Unnecessary Complexity
*Weakness BaseWeakness BaseUse of Less Trusted Source - (348)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 348 (Use of Less Trusted Source)
The software 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.
*Weakness ClassWeakness ClassViolation of Secure Design Principles - (657)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 975 (SFP Secondary Cluster: Architecture) > 657 (Violation of Secure Design Principles)
The product violates well-established principles for secure design.
+CategoryCategorySFP Secondary Cluster: Compiler - (976)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 976 (SFP Secondary Cluster: Compiler)
This category identifies Software Fault Patterns (SFPs) within the Compiler cluster.
*Weakness BaseWeakness BaseCompiler Optimization Removal or Modification of Security-critical Code - (733)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 976 (SFP Secondary Cluster: Compiler) > 733 (Compiler Optimization Removal or Modification of Security-critical Code)
The developer builds a security-critical protection mechanism into the software but the compiler optimizes the program such that the mechanism is removed or modified.
+CategoryCategorySFP Secondary Cluster: Design - (977)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design)
This category identifies Software Fault Patterns (SFPs) within the Design cluster.
*Weakness BaseWeakness BaseAcceptance of Extraneous Untrusted Data With Trusted Data - (349)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 349 (Acceptance of Extraneous Untrusted Data With Trusted Data)
The software, 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.
*Weakness BaseWeakness BaseAddition of Data Structure Sentinel - (464)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 464 (Addition of Data Structure Sentinel)
The accidental addition of a data-structure sentinel can cause serious programming logic problems.
*Weakness BaseWeakness BaseAlgorithmic Complexity - (407)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 407 (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.
*Weakness ClassWeakness ClassAlways-Incorrect Control Flow Implementation - (670)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 670 (Always-Incorrect Control Flow Implementation)
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.
*Weakness ClassWeakness ClassAsymmetric Resource Consumption (Amplification) - (405)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 405 (Asymmetric Resource Consumption (Amplification))
Software that does not appropriately monitor or control resource consumption can lead to adverse system performance.
*Weakness BaseWeakness BaseComparison of Object References Instead of Object Contents - (595)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 595 (Comparison of Object References Instead of Object Contents)
The program compares object references instead of the contents of the objects themselves, preventing it from detecting equivalent objects.
*Weakness BaseWeakness BaseDeletion of Data Structure Sentinel - (463)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 463 (Deletion of Data Structure Sentinel)
The accidental deletion of a data-structure sentinel can cause serious programming logic problems.
*Weakness BaseWeakness BaseDeployment of Wrong Handler - (430)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 430 (Deployment of Wrong Handler)
The wrong "handler" is assigned to process an object.
*Weakness BaseWeakness BaseDuplicate Key in Associative List (Alist) - (462)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 462 (Duplicate Key in Associative List (Alist))
Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error.
*Weakness BaseWeakness BaseExecution After Redirect (EAR) - (698)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 698 (Execution After Redirect (EAR))
The web application sends a redirect to another location, but instead of exiting, it executes additional code.Redirect Without Exit
*Weakness BaseWeakness BaseExposed Unsafe ActiveX Method - (618)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 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).
*Weakness BaseWeakness BaseImproper Handling of Highly Compressed Data (Data Amplification) - (409)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 409 (Improper Handling of Highly Compressed Data (Data Amplification))
The software does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.
*Weakness ClassWeakness ClassIncorrect Behavior Order - (696)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 696 (Incorrect Behavior Order)
The software performs multiple related behaviors, but the behaviors are performed in the wrong order in ways which may produce resultant weaknesses.
*Weakness BaseWeakness BaseIncorrect Behavior Order: Early Amplification - (408)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 408 (Incorrect Behavior Order: Early Amplification)
The software allows an entity to perform a legitimate but expensive operation before authentication or authorization has taken place.
*Weakness VariantWeakness VariantIncorrect Block Delimitation - (483)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 483 (Incorrect Block Delimitation)
The code does not explicitly delimit a block that is intended to contain 2 or more statements, creating a logic error.
*Weakness ClassWeakness ClassIncorrect Calculation - (682)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 682 (Incorrect Calculation)
The software performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.
*Weakness ClassWeakness ClassIncorrect Control Flow Scoping - (705)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 705 (Incorrect Control Flow Scoping)
The software does not properly return control flow to the proper location after it has completed a task or detected an unusual condition.
*Weakness BaseWeakness BaseIncorrect Semantic Object Comparison - (596)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 596 (Incorrect Semantic Object Comparison)
The software does not correctly compare two objects based on their conceptual content.
*Weakness BaseWeakness BaseIncorrect Use of Privileged APIs - (648)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 648 (Incorrect Use of Privileged APIs)
The application 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.
*Weakness ClassWeakness ClassInsufficient Comparison - (697)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 697 (Insufficient Comparison)
The software compares two entities in a security-relevant context, but the comparison is insufficient, which may lead to resultant weaknesses.
*Weakness ClassWeakness ClassInsufficient Control Flow Management - (691)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 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.
*Weakness BaseWeakness BaseInsufficient Control of Network Message Volume (Network Amplification) - (406)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 406 (Insufficient Control of Network Message Volume (Network Amplification))
The software does not sufficiently monitor or control transmitted network traffic volume, so that an actor can cause the software to transmit more traffic than should be allowed for that actor.
*Weakness BaseWeakness BaseInsufficient Resource Pool - (410)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 410 (Insufficient Resource Pool)
The software'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.
*Weakness BaseWeakness BaseMisinterpretation of Input - (115)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 115 (Misinterpretation of Input)
The software misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.
*Weakness BaseWeakness BaseObject Model Violation: Just One of Equals and Hashcode Defined - (581)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 581 (Object Model Violation: Just One of Equals and Hashcode Defined)
The software does not maintain equal hashcodes for equal objects.
*Weakness BaseWeakness BaseOff-by-one Error - (193)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 193 (Off-by-one Error)
A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.off-by-five
*Weakness BaseWeakness BasePartial Comparison - (187)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 187 (Partial Comparison)
The software 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.
*Weakness BaseWeakness BaseReliance on Data/Memory Layout - (188)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 188 (Reliance on Data/Memory Layout)
The software makes invalid assumptions about how protocol data or memory is organized at a lower level, resulting in unintended program behavior.
*Weakness BaseWeakness BaseUse of Incorrect Operator - (480)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 977 (SFP Secondary Cluster: Design) > 480 (Use of Incorrect Operator)
The programmer accidentally uses the wrong operator, which changes the application logic in security-relevant ways.
+CategoryCategorySFP Secondary Cluster: Implementation - (978)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 978 (SFP Secondary Cluster: Implementation)
This category identifies Software Fault Patterns (SFPs) within the Implementation cluster.
*Weakness ClassWeakness ClassCoding Standards Violation - (710)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 978 (SFP Secondary Cluster: Implementation) > 710 (Coding Standards Violation)
The software does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.
*Weakness ClassWeakness ClassContainment Errors (Container Errors) - (216)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 978 (SFP Secondary Cluster: Implementation) > 216 (Containment Errors (Container Errors))
This tries to cover various problems in which improper data are included within a "container."
*Weakness BaseWeakness BaseImproperly Implemented Security Check for Standard - (358)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 978 (SFP Secondary Cluster: Implementation) > 358 (Improperly Implemented Security Check for Standard)
The software does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.
*Weakness ClassWeakness ClassIndicator of Poor Code Quality - (398)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 978 (SFP Secondary Cluster: Implementation) > 398 (Indicator of Poor Code Quality)
The code has features that do not directly introduce a weakness or vulnerability, but indicate that the product has not been carefully developed or maintained.
*Weakness VariantWeakness VariantUnsafe ActiveX Control Marked Safe For Scripting - (623)
888 (Software Fault Pattern (SFP) Clusters) > 907 (SFP Primary Cluster: Other) > 978 (SFP Secondary Cluster: Implementation) > 623 (Unsafe ActiveX Control Marked Safe For Scripting)
An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.
+CategoryCategorySFP Primary Cluster: Path Resolution - (893)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution)
This category identifies Software Fault Patterns (SFPs) within the Path Resolution cluster.
+CategoryCategorySFP Secondary Cluster: Failed Chroot Jail - (979)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 979 (SFP Secondary Cluster: Failed Chroot Jail)
This category identifies Software Fault Patterns (SFPs) within the Failed Chroot Jail cluster.
*Weakness VariantWeakness VariantCreation of chroot Jail Without Changing Working Directory - (243)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 979 (SFP Secondary Cluster: Failed Chroot Jail) > 243 (Creation of chroot Jail Without Changing Working Directory)
The program uses the chroot() system call to create a jail, but does not change the working directory afterward. This does not prevent access to files outside of the jail.
+CategoryCategorySFP Secondary Cluster: Link in Resource Name Resolution - (980)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 980 (SFP Secondary Cluster: Link in Resource Name Resolution)
This category identifies Software Fault Patterns (SFPs) within the Link in Resource Name Resolution cluster.
*Weakness VariantWeakness VariantApple '.DS_Store' - (71)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 980 (SFP Secondary Cluster: Link in Resource Name Resolution) > 71 (Apple '.DS_Store')
Software operating in a MAC OS environment, where .DS_Store is in effect, must carefully manage hard links, otherwise an attacker may be able to leverage a hard link from .DS_Store to overwrite arbitrary files and gain privileges.
*Weakness ClassWeakness ClassExternally Controlled Reference to a Resource in Another Sphere - (610)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 980 (SFP Secondary Cluster: Link in Resource Name Resolution) > 610 (Externally Controlled Reference to a Resource in Another Sphere)
The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.
*Weakness BaseWeakness BaseImproper Link Resolution Before File Access ('Link Following') - (59)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 980 (SFP Secondary Cluster: Link in Resource Name Resolution) > 59 (Improper Link Resolution Before File Access ('Link Following'))
The software 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.insecure temporary file
*Weakness BaseWeakness BaseSymbolic Name not Mapping to Correct Object - (386)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 980 (SFP Secondary Cluster: Link in Resource Name Resolution) > 386 (Symbolic Name not Mapping to Correct Object)
A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.
*Weakness VariantWeakness VariantUNIX Hard Link - (62)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 980 (SFP Secondary Cluster: Link in Resource Name Resolution) > 62 (UNIX Hard Link)
The software, 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 software to operate on unauthorized files.
*Weakness VariantWeakness VariantWindows Hard Link - (65)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 980 (SFP Secondary Cluster: Link in Resource Name Resolution) > 65 (Windows Hard Link)
The software, 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 software to operate on unauthorized files.
*Weakness VariantWeakness VariantWindows Shortcut Following (.LNK) - (64)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 980 (SFP Secondary Cluster: Link in Resource Name Resolution) > 64 (Windows Shortcut Following (.LNK))
The software, when opening a file or directory, does not sufficiently handle when the file is a Windows shortcut (.LNK) whose target is outside of the intended control sphere. This could allow an attacker to cause the software to operate on unauthorized files.Windows symbolic link followingsymlink
+CategoryCategorySFP Secondary Cluster: Path Traversal - (981)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal)
This category identifies Software Fault Patterns (SFPs) within the Path Traversal cluster.
*Weakness BaseWeakness BaseAbsolute Path Traversal - (36)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 36 (Absolute Path Traversal)
The software 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.
*Weakness ClassWeakness ClassExternal Control of File Name or Path - (73)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 73 (External Control of File Name or Path)
The software allows user input to control or influence paths or file names that are used in filesystem operations.
*Weakness VariantWeakness VariantImproper Handling of Apple HFS+ Alternate Data Stream Path - (72)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 72 (Improper Handling of Apple HFS+ Alternate Data Stream Path)
The software does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system.
*Weakness BaseWeakness BaseImproper Handling of File Names that Identify Virtual Resources - (66)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 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.
*Weakness VariantWeakness VariantImproper Handling of Windows Device Names - (67)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 67 (Improper Handling of Windows Device Names)
The software 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.
*Weakness ClassWeakness ClassImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') - (22)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 22 (Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'))
The software 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 software 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.Directory traversalPath traversal
*Weakness BaseWeakness BaseImproper Resolution of Path Equivalence - (41)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 41 (Improper Resolution of Path Equivalence)
The system or application 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.
*Weakness VariantWeakness VariantPath Equivalence: ' filename' (Leading Space) - (47)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 47 (Path Equivalence: ' filename' (Leading Space))
A software system that accepts path input in the form of leading space (' filedir') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: '/./' (Single Dot Directory) - (55)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 55 (Path Equivalence: '/./' (Single Dot Directory))
A software system that accepts path input in the form of single dot directory exploit ('/./') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: '//multiple/leading/slash' - (50)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 50 (Path Equivalence: '//multiple/leading/slash')
A software system that accepts path input in the form of multiple leading slash ('//multiple/leading/slash') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: '/multiple//internal/slash' - (51)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 51 (Path Equivalence: '/multiple//internal/slash')
A software system that accepts path input in the form of multiple internal slash ('/multiple//internal/slash/') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: '/multiple/trailing/slash//' - (52)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 52 (Path Equivalence: '/multiple/trailing/slash//')
A software system that accepts path input in the form of multiple trailing slash ('/multiple/trailing/slash//') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: '\multiple\\internal\backslash' - (53)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 53 (Path Equivalence: '\multiple\\internal\backslash')
A software system that accepts path input in the form of multiple internal backslash ('\multiple\trailing\\slash') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: 'fakedir/../realdir/filename' - (57)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 57 (Path Equivalence: 'fakedir/../realdir/filename')
The software contains protection mechanisms to restrict access to 'realdir/filename', but it constructs pathnames using external input in the form of 'fakedir/../realdir/filename' that are not handled by those mechanisms. This allows attackers to perform unauthorized actions against the targeted file.
*Weakness VariantWeakness VariantPath Equivalence: 'file name' (Internal Whitespace) - (48)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 48 (Path Equivalence: 'file name' (Internal Whitespace))
A software system that accepts path input in the form of internal space ('file(SPACE)name') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: 'file...name' (Multiple Internal Dot) - (45)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 45 (Path Equivalence: 'file...name' (Multiple Internal Dot))
A software system that accepts path input in the form of multiple internal dot ('file...dir') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: 'file.name' (Internal Dot) - (44)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 44 (Path Equivalence: 'file.name' (Internal Dot))
A software system that accepts path input in the form of internal dot ('file.ordir') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: 'filedir*' (Wildcard) - (56)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 56 (Path Equivalence: 'filedir*' (Wildcard))
A software system that accepts path input in the form of asterisk wildcard ('filedir*') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: 'filedir\' (Trailing Backslash) - (54)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 54 (Path Equivalence: 'filedir\' (Trailing Backslash))
A software system that accepts path input in the form of trailing backslash ('filedir\') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: 'filename ' (Trailing Space) - (46)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 46 (Path Equivalence: 'filename ' (Trailing Space))
A software system that accepts path input in the form of trailing space ('filedir ') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: 'filename.' (Trailing Dot) - (42)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 42 (Path Equivalence: 'filename.' (Trailing Dot))
A software system that accepts path input in the form of trailing dot ('filedir.') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: 'filename....' (Multiple Trailing Dot) - (43)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 43 (Path Equivalence: 'filename....' (Multiple Trailing Dot))
A software system that accepts path input in the form of multiple trailing dot ('filedir....') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: 'filename/' (Trailing Slash) - (49)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 49 (Path Equivalence: 'filename/' (Trailing Slash))
A software system that accepts path input in the form of trailing slash ('filedir/') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Equivalence: Windows 8.3 Filename - (58)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 58 (Path Equivalence: Windows 8.3 Filename)
The software contains a protection mechanism that restricts access to a long filename on a Windows operating system, but the software does not properly restrict access to the equivalent short "8.3" filename.
*Weakness VariantWeakness VariantPath Traversal: '...' (Triple Dot) - (32)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 32 (Path Traversal: '...' (Triple Dot))
The software 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.
*Weakness VariantWeakness VariantPath Traversal: '....' (Multiple Dot) - (33)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 33 (Path Traversal: '....' (Multiple Dot))
The software uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '....' (multiple dot) sequences that can resolve to a location that is outside of that directory.
*Weakness VariantWeakness VariantPath Traversal: '....//' - (34)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 34 (Path Traversal: '....//')
The software uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '....//' (doubled dot dot slash) sequences that can resolve to a location that is outside of that directory.
*Weakness VariantWeakness VariantPath Traversal: '.../...//' - (35)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 35 (Path Traversal: '.../...//')
The software 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.
*Weakness VariantWeakness VariantPath Traversal: '../filedir' - (24)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 24 (Path Traversal: '../filedir')
The software 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.
*Weakness VariantWeakness VariantPath Traversal: '..\filedir' - (28)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 28 (Path Traversal: '..\filedir')
The software 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.
*Weakness VariantWeakness VariantPath Traversal: '/../filedir' - (25)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 25 (Path Traversal: '/../filedir')
The software 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.
*Weakness VariantWeakness VariantPath Traversal: '/absolute/pathname/here' - (37)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 37 (Path Traversal: '/absolute/pathname/here')
A software system that accepts input in the form of a slash absolute path ('/absolute/pathname/here') without appropriate validation can allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Traversal: '/dir/../filename' - (26)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 26 (Path Traversal: '/dir/../filename')
The software 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.
*Weakness VariantWeakness VariantPath Traversal: 'C:dirname' - (39)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 39 (Path Traversal: 'C:dirname')
An attacker can inject a drive letter or Windows volume letter ('C:dirname') into a software system to potentially redirect access to an unintended location or arbitrary file.
*Weakness VariantWeakness VariantPath Traversal: '\..\filename' - (29)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 29 (Path Traversal: '\..\filename')
The software 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.
*Weakness VariantWeakness VariantPath Traversal: '\\UNC\share\name\' (Windows UNC Share) - (40)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 40 (Path Traversal: '\\UNC\share\name\' (Windows UNC Share))
An attacker can inject a Windows UNC share ('\\UNC\share\name') into a software system to potentially redirect access to an unintended location or arbitrary file.
*Weakness VariantWeakness VariantPath Traversal: '\absolute\pathname\here' - (38)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 38 (Path Traversal: '\absolute\pathname\here')
A software system that accepts input in the form of a backslash absolute path ('\absolute\pathname\here') without appropriate validation can allow an attacker to traverse the file system to unintended locations or access arbitrary files.
*Weakness VariantWeakness VariantPath Traversal: '\dir\..\filename' - (30)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 30 (Path Traversal: '\dir\..\filename')
The software uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\dir\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.
*Weakness VariantWeakness VariantPath Traversal: 'dir/../../filename' - (27)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 27 (Path Traversal: 'dir/../../filename')
The software 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.
*Weakness VariantWeakness VariantPath Traversal: 'dir\..\..\filename' - (31)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 31 (Path Traversal: 'dir\..\..\filename')
The software uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize 'dir\..\..\filename' (multiple internal backslash dot dot) sequences that can resolve to a location that is outside of that directory.
*Weakness BaseWeakness BaseRelative Path Traversal - (23)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 23 (Relative Path Traversal)
The software 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.
*Weakness BaseWeakness BaseUnquoted Search Path or Element - (428)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 428 (Unquoted Search Path or Element)
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.
*Weakness ClassWeakness ClassUse of Incorrectly-Resolved Name or Reference - (706)
888 (Software Fault Pattern (SFP) Clusters) > 893 (SFP Primary Cluster: Path Resolution) > 981 (SFP Secondary Cluster: Path Traversal) > 706 (Use of Incorrectly-Resolved Name or Reference)
The software 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.
+CategoryCategorySFP Primary Cluster: Predictability - (905)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability)
This category identifies Software Fault Patterns (SFPs) within the Predictability cluster.
*Weakness VariantWeakness VariantImproper Handling of Insufficient Entropy in TRNG - (333)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 333 (Improper Handling of Insufficient Entropy in TRNG)
True random number generators (TRNG) generally have a limited source of entropy and therefore can fail or block.
*Weakness BaseWeakness BaseInsufficient Entropy - (331)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 331 (Insufficient Entropy)
The software uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
*Weakness VariantWeakness VariantInsufficient Entropy in PRNG - (332)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 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.
*Weakness ClassWeakness ClassPRNG Seed Error - (335)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 335 (PRNG Seed Error)
A Pseudo-Random Number Generator (PRNG) uses seeds incorrectly.
*Weakness ClassWeakness ClassPredictability Problems - (340)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 340 (Predictability Problems)
Weaknesses in this category are related to schemes that generate numbers or identifiers that are more predictable than required by the application.
*Weakness BaseWeakness BasePredictable Exact Value from Previous Values - (342)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 342 (Predictable Exact Value from Previous Values)
An exact value or random number can be precisely predicted by observing previous values.
*Weakness BaseWeakness BasePredictable Seed in PRNG - (337)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 337 (Predictable Seed in PRNG)
A PRNG is initialized from a predictable seed, e.g. using process ID or system time.
*Weakness BaseWeakness BasePredictable Value Range from Previous Values - (343)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 343 (Predictable Value Range from Previous Values)
The software'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.
*Weakness BaseWeakness BasePredictable from Observable State - (341)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 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.
*Weakness BaseWeakness BaseSame Seed in PRNG - (336)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 336 (Same Seed in PRNG)
A PRNG uses the same seed each time the product is initialized. If an attacker can guess (or knows) the seed, then he/she may be able to determine the "random" number produced from the PRNG.
*Weakness BaseWeakness BaseSmall Seed Space in PRNG - (339)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 339 (Small Seed Space in PRNG)
A PRNG uses a relatively small space of seeds.
*Weakness BaseWeakness BaseSmall Space of Random Values - (334)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 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.
*Weakness BaseWeakness BaseUse of Cryptographically Weak Pseudo-Random Number Generator (PRNG) - (338)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))
The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG is not cryptographically strong.
*Weakness ClassWeakness ClassUse of Insufficiently Random Values - (330)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 330 (Use of Insufficiently Random Values)
The software may use insufficiently random numbers or values in a security context that depends on unpredictable numbers.
*Weakness BaseWeakness BaseUse of Invariant Value in Dynamically Changing Context - (344)
888 (Software Fault Pattern (SFP) Clusters) > 905 (SFP Primary Cluster: Predictability) > 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.
+CategoryCategorySFP Primary Cluster: Privilege - (901)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege)
This category identifies Software Fault Patterns (SFPs) within the Privilege cluster.
*Weakness VariantWeakness Variant.NET Misconfiguration: Use of Impersonation - (520)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 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.
*Weakness ClassWeakness ClassExecution with Unnecessary Privileges - (250)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 250 (Execution with Unnecessary Privileges)
The software 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.
*Weakness BaseWeakness BaseImproper Handling of Insufficient Privileges - (274)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 274 (Improper Handling of Insufficient Privileges)
The software does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses.
*Weakness BaseWeakness BaseImproper Privilege Management - (269)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 269 (Improper Privilege Management)
The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
*Weakness BaseWeakness BaseIncorrect Privilege Assignment - (266)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 266 (Incorrect Privilege Assignment)
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
*Weakness BaseWeakness BaseInsufficient Compartmentalization - (653)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 653 (Insufficient Compartmentalization)
The product does not sufficiently compartmentalize functionality or processes that require different privilege levels, rights, or permissions.Separation of Privilege
*Weakness VariantWeakness VariantJ2EE Misconfiguration: Weak Access Permissions for EJB Methods - (9)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 9 (J2EE Misconfiguration: Weak Access Permissions for EJB Methods)
If elevated access rights are assigned to EJB methods, then an attacker can take advantage of the permissions to exploit the software system.
*Weakness BaseWeakness BaseLeast Privilege Violation - (272)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 272 (Least Privilege Violation)
The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.
*Weakness BaseWeakness BasePrivilege Chaining - (268)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 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.
*Weakness BaseWeakness BasePrivilege Context Switching Error - (270)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 270 (Privilege Context Switching Error)
The software does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.
*Weakness BaseWeakness BasePrivilege Defined With Unsafe Actions - (267)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 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.
*Weakness ClassWeakness ClassPrivilege Dropping / Lowering Errors - (271)
888 (Software Fault Pattern (SFP) Clusters) > 901 (SFP Primary Cluster: Privilege) > 271 (Privilege Dropping / Lowering Errors)
The software does not drop privileges before passing control of a resource to an actor that does not have those privileges.
+CategoryCategorySFP Primary Cluster: Resource Management - (892)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management)
This category identifies Software Fault Patterns (SFPs) within the Resource Management cluster.
+CategoryCategorySFP Secondary Cluster: Failure to Release Resource - (982)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 982 (SFP Secondary Cluster: Failure to Release Resource)
This category identifies Software Fault Patterns (SFPs) within the Failure to Release Resource cluster.
*Weakness BaseWeakness BaseImproper Release of Memory Before Removing Last Reference ('Memory Leak') - (401)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 982 (SFP Secondary Cluster: Failure to Release Resource) > 401 (Improper Release of Memory Before Removing Last Reference ('Memory Leak'))
The software does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.Memory Leak
*Weakness BaseWeakness BaseImproper Resource Shutdown or Release - (404)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 982 (SFP Secondary Cluster: Failure to Release Resource) > 404 (Improper Resource Shutdown or Release)
The program does not release or incorrectly releases a resource before it is made available for re-use.
*Weakness BaseWeakness BaseIncomplete Cleanup - (459)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 982 (SFP Secondary Cluster: Failure to Release Resource) > 459 (Incomplete Cleanup)
The software does not properly "clean up" and remove temporary or supporting resources after they have been used.Insufficient Cleanup
*Weakness BaseWeakness BaseMissing Reference to Active Allocated Resource - (771)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 982 (SFP Secondary Cluster: Failure to Release Resource) > 771 (Missing Reference to Active Allocated Resource)
The software does not properly maintain a reference to a resource that has been allocated, which prevents the resource from being reclaimed.
*Weakness VariantWeakness VariantMissing Reference to Active File Descriptor or Handle - (773)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 982 (SFP Secondary Cluster: Failure to Release Resource) > 773 (Missing Reference to Active File Descriptor or Handle)
The software does not properly maintain references to a file descriptor or handle, which prevents that file descriptor/handle from being reclaimed.
*Weakness VariantWeakness VariantMissing Release of File Descriptor or Handle after Effective Lifetime - (775)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 982 (SFP Secondary Cluster: Failure to Release Resource) > 775 (Missing Release of File Descriptor or Handle after Effective Lifetime)
The software 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.
*Weakness BaseWeakness BaseMissing Release of Resource after Effective Lifetime - (772)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 982 (SFP Secondary Cluster: Failure to Release Resource) > 772 (Missing Release of Resource after Effective Lifetime)
The software does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
+CategoryCategorySFP Secondary Cluster: Faulty Resource Use - (983)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 983 (SFP Secondary Cluster: Faulty Resource Use)
This category identifies Software Fault Patterns (SFPs) within the Faulty Resource Use cluster.
*Weakness BaseWeakness BaseOperation on a Resource after Expiration or Release - (672)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 983 (SFP Secondary Cluster: Faulty Resource Use) > 672 (Operation on a Resource after Expiration or Release)
The software uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.
*Weakness BaseWeakness BaseUse After Free - (416)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 983 (SFP Secondary Cluster: Faulty Resource Use) > 416 (Use After Free)
Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.Dangling pointerUse-After-Free
+CategoryCategorySFP Secondary Cluster: Life Cycle - (984)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 984 (SFP Secondary Cluster: Life Cycle)
This category identifies Software Fault Patterns (SFPs) within the Life Cycle cluster.
*Weakness ClassWeakness ClassDuplicate Operations on Resource - (675)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 984 (SFP Secondary Cluster: Life Cycle) > 675 (Duplicate Operations on Resource)
The product performs the same operation on a resource two or more times, when the operation should only be applied once.
*Weakness ClassWeakness ClassImproper Control of a Resource Through its Lifetime - (664)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 984 (SFP Secondary Cluster: Life Cycle) > 664 (Improper Control of a Resource Through its Lifetime)
The software does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.
*Weakness BaseWeakness BaseOperation on Resource in Wrong Phase of Lifetime - (666)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 984 (SFP Secondary Cluster: Life Cycle) > 666 (Operation on Resource in Wrong Phase of Lifetime)
The software performs an operation on a resource at the wrong phase of the resource's lifecycle, which can lead to unexpected behaviors.
*Weakness BaseWeakness BaseUse of Multiple Resources with Duplicate Identifier - (694)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 984 (SFP Secondary Cluster: Life Cycle) > 694 (Use of Multiple Resources with Duplicate Identifier)
The software uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.
+CategoryCategorySFP Secondary Cluster: Unrestricted Consumption - (985)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 985 (SFP Secondary Cluster: Unrestricted Consumption)
This category identifies Software Fault Patterns (SFPs) within the Unrestricted Consumption cluster.
*Weakness VariantWeakness VariantAllocation of File Descriptors or Handles Without Limits or Throttling - (774)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 985 (SFP Secondary Cluster: Unrestricted Consumption) > 774 (Allocation of File Descriptors or Handles Without Limits or Throttling)
The software 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.
*Weakness BaseWeakness BaseAllocation of Resources Without Limits or Throttling - (770)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 985 (SFP Secondary Cluster: Unrestricted Consumption) > 770 (Allocation of Resources Without Limits or Throttling)
The software allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on how many resources can be allocated, in violation of the intended security policy for that actor.
*Weakness BaseWeakness BaseUncontrolled Recursion - (674)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 985 (SFP Secondary Cluster: Unrestricted Consumption) > 674 (Uncontrolled Recursion)
The product does not properly control the amount of recursion that takes place, which consumes excessive resources, such as allocated memory or the program stack.Stack Exhaustion
*Weakness BaseWeakness BaseUncontrolled Resource Consumption ('Resource Exhaustion') - (400)
888 (Software Fault Pattern (SFP) Clusters) > 892 (SFP Primary Cluster: Resource Management) > 985 (SFP Secondary Cluster: Unrestricted Consumption) > 400 (Uncontrolled Resource Consumption ('Resource Exhaustion'))
The software does not properly restrict the size or amount of resources that are requested or influenced by an actor, which can be used to consume more resources than intended.
+CategoryCategorySFP Primary Cluster: Risky Values - (885)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values)
This category identifies Software Fault Patterns (SFPs) within the Risky Values cluster.
+CategoryCategorySFP Secondary Cluster: Glitch in Computation - (998)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation)
This category identifies Software Fault Patterns (SFPs) within the Glitch in Computation cluster.
*Weakness VariantWeakness VariantAssigning instead of Comparing - (481)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 481 (Assigning instead of Comparing)
The code uses an operator for assignment when the intention was to perform a comparison.
*Weakness BaseWeakness BaseAssignment of a Fixed Address to a Pointer - (587)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 587 (Assignment of a Fixed Address to a Pointer)
The software sets a pointer to a specific address other than NULL or 0.
*Weakness VariantWeakness VariantComparison of Classes by Name - (486)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 486 (Comparison of Classes by Name)
The program compares classes by name, which can cause it to use the wrong class when multiple classes can have the same name.
*Weakness BaseWeakness BaseDivide By Zero - (369)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 369 (Divide By Zero)
The product divides a value by zero.
*Weakness VariantWeakness VariantExpression is Always False - (570)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 570 (Expression is Always False)
The software contains an expression that will always evaluate to false.
*Weakness VariantWeakness VariantExpression is Always True - (571)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 571 (Expression is Always True)
The software contains an expression that will always evaluate to true.
*Weakness VariantWeakness VariantFunction Call With Incorrect Argument Type - (686)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 686 (Function Call With Incorrect Argument Type)
The software calls a function, procedure, or routine, but the caller specifies an argument that is the wrong data type, which may lead to resultant weaknesses.
*Weakness VariantWeakness VariantFunction Call With Incorrect Number of Arguments - (685)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 685 (Function Call With Incorrect Number of Arguments)
The software calls a function, procedure, or routine, but the caller specifies too many arguments, or too few arguments, which may lead to undefined behavior and resultant weaknesses.
*Weakness VariantWeakness VariantFunction Call With Incorrect Order of Arguments - (683)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 683 (Function Call With Incorrect Order of Arguments)
The software calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses.
*Weakness VariantWeakness VariantFunction Call With Incorrect Variable or Reference as Argument - (688)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 688 (Function Call With Incorrect Variable or Reference as Argument)
The software calls a function, procedure, or routine, but the caller specifies the wrong variable or reference as one of the arguments, which may lead to undefined behavior and resultant weaknesses.
*Weakness VariantWeakness VariantFunction Call With Incorrectly Specified Argument Value - (687)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 687 (Function Call With Incorrectly Specified Argument Value)
The software calls a function, procedure, or routine, but the caller specifies an argument that contains the wrong value, which may lead to resultant weaknesses.
*Weakness BaseWeakness BaseFunction Call with Incorrectly Specified Arguments - (628)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 628 (Function Call with Incorrectly Specified Arguments)
The product calls a function, procedure, or routine with arguments that are not correctly specified, leading to always-incorrect behavior and resultant weaknesses.
*Weakness BaseWeakness BaseIncorrect Conversion between Numeric Types - (681)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 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.
*Weakness BaseWeakness BaseIncorrect Pointer Scaling - (468)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 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.
*Weakness VariantWeakness VariantIncorrect Short Circuit Evaluation - (768)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 768 (Incorrect Short Circuit Evaluation)
The software contains a conditional statement with multiple logical expressions in which one of the non-leading expressions may produce side effects. This may lead to an unexpected state in the program after the execution of the conditional, because short-circuiting logic may prevent the side effects from occurring.
*Weakness ClassWeakness ClassIncorrect Type Conversion or Cast - (704)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 704 (Incorrect Type Conversion or Cast)
The software does not correctly convert an object, resource or structure from one type to a different type.
*Weakness BaseWeakness BaseInteger Overflow or Wraparound - (190)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 190 (Integer Overflow or Wraparound)
The software 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.
*Weakness BaseWeakness BaseInteger Underflow (Wrap or Wraparound) - (191)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 191 (Integer Underflow (Wrap or Wraparound))
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.Integer underflow
*Weakness VariantWeakness VariantJ2EE Bad Practices: Non-serializable Object Stored in Session - (579)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 579 (J2EE Bad Practices: Non-serializable Object Stored in Session)
The application stores a non-serializable object as an HttpSession attribute, which can hurt reliability.
*Weakness VariantWeakness VariantJ2EE Framework: Saving Unserializable Objects to Disk - (594)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 594 (J2EE Framework: Saving Unserializable Objects to Disk)
When the J2EE container attempts to write unserializable objects to disk there is no guarantee that the process will complete successfully.
*Weakness BaseWeakness BaseMissing Initialization of a Variable - (456)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 456 (Missing Initialization of a Variable)
The software does not initialize critical variables, which causes the execution environment to use unexpected values.
*Weakness BaseWeakness BaseNumeric Truncation Error - (197)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 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.
*Weakness BaseWeakness BaseReturn of Pointer Value Outside of Expected Range - (466)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 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.
*Weakness BaseWeakness BaseReturn of Stack Variable Address - (562)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 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.
*Weakness VariantWeakness VariantSigned to Unsigned Conversion Error - (195)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 195 (Signed to Unsigned Conversion Error)
The software 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.
*Weakness BaseWeakness BaseUndefined Behavior for Input to API - (475)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 475 (Undefined Behavior for Input to API)
The behavior of this function is undefined unless its control parameter is set to a specific value.
*Weakness BaseWeakness BaseUnexpected Sign Extension - (194)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 194 (Unexpected Sign Extension)
The software 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.
*Weakness VariantWeakness VariantUnsigned to Signed Conversion Error - (196)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 196 (Unsigned to Signed Conversion Error)
The software 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.
*Weakness VariantWeakness VariantUse of Uninitialized Variable - (457)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 457 (Use of Uninitialized Variable)
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
*Weakness VariantWeakness VariantUse of Wrong Operator in String Comparison - (597)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 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.
*Weakness BaseWeakness BaseWrap-around Error - (128)
888 (Software Fault Pattern (SFP) Clusters) > 885 (SFP Primary Cluster: Risky Values) > 998 (SFP Secondary Cluster: Glitch in Computation) > 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.
+CategoryCategorySFP Primary Cluster: Synchronization - (894)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization)
This category identifies Software Fault Patterns (SFPs) within the Synchronization cluster.
+CategoryCategorySFP Secondary Cluster: Missing Lock - (986)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock)
This category identifies Software Fault Patterns (SFPs) within the Missing Lock cluster.
*Weakness BaseWeakness BaseContext Switching Race Condition - (368)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 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.
*Weakness BaseWeakness BaseDouble-Checked Locking - (609)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 609 (Double-Checked Locking)
The program uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient.
*Weakness BaseWeakness BaseImproper Locking - (667)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 667 (Improper Locking)
The software does not properly acquire a lock on a resource, or it does not properly release a lock on a resource, leading to unexpected resource state changes and behaviors.
*Weakness BaseWeakness BaseImproper Resource Locking - (413)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 413 (Improper Resource Locking)
The software does not lock or does not correctly lock a resource when the software must have exclusive access to the resource.
*Weakness BaseWeakness BaseImproper Synchronization - (662)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 662 (Improper Synchronization)
The software attempts to use a shared resource in an exclusive manner, but does not prevent or incorrectly prevents use of the resource by another thread or process.
*Weakness BaseWeakness BaseMissing Lock Check - (414)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 414 (Missing Lock Check)
A product does not check to see if a lock is present before performing sensitive operations on a resource.
*Weakness BaseWeakness BaseRace Condition in Switch - (365)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 365 (Race Condition in Switch)
The code contains a switch statement in which the switched variable can be modified while the switch is still executing, resulting in unexpected behavior.
*Weakness BaseWeakness BaseRace Condition within a Thread - (366)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 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.
*Weakness BaseWeakness BaseSignal Handler Race Condition - (364)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 364 (Signal Handler Race Condition)
The software uses a signal handler that introduces a race condition.
*Weakness BaseWeakness BaseUnsynchronized Access to Shared Data in a Multithreaded Context - (567)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 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.
*Weakness VariantWeakness VariantUse of Singleton Pattern Without Synchronization in a Multithreaded Context - (543)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 543 (Use of Singleton Pattern Without Synchronization in a Multithreaded Context)
The software uses the singleton pattern when creating a resource within a multithreaded environment.
*Weakness BaseWeakness BaseUse of a Non-reentrant Function in a Concurrent Context - (663)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 986 (SFP Secondary Cluster: Missing Lock) > 663 (Use of a Non-reentrant Function in a Concurrent Context)
The software calls a non-reentrant function in a concurrent context in which a competing code sequence (e.g. thread or signal handler) may have an opportunity to call the same function or otherwise influence its state.
+CategoryCategorySFP Secondary Cluster: Multiple Locks/Unlocks - (987)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 987 (SFP Secondary Cluster: Multiple Locks/Unlocks)
This category identifies Software Fault Patterns (SFPs) within the Multiple Locks/Unlocks cluster.
*Weakness VariantWeakness VariantEmpty Synchronized Block - (585)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 987 (SFP Secondary Cluster: Multiple Locks/Unlocks) > 585 (Empty Synchronized Block)
The software contains an empty synchronized block.
*Weakness VariantWeakness VariantMultiple Locks of a Critical Resource - (764)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 987 (SFP Secondary Cluster: Multiple Locks/Unlocks) > 764 (Multiple Locks of a Critical Resource)
The software locks a critical resource more times than intended, leading to an unexpected state in the system.
*Weakness VariantWeakness VariantMultiple Unlocks of a Critical Resource - (765)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 987 (SFP Secondary Cluster: Multiple Locks/Unlocks) > 765 (Multiple Unlocks of a Critical Resource)
The software unlocks a critical resource more times than intended, leading to an unexpected state in the system.
+CategoryCategorySFP Secondary Cluster: Race Condition Window - (988)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 988 (SFP Secondary Cluster: Race Condition Window)
This category identifies Software Fault Patterns (SFPs) within the Race Condition Window cluster.
*Weakness ClassWeakness ClassConcurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') - (362)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 988 (SFP Secondary Cluster: Race Condition Window) > 362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'))
The program 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.
*Weakness BaseWeakness BaseMissing Check for Certificate Revocation after Initial Check - (370)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 988 (SFP Secondary Cluster: Race Condition Window) > 370 (Missing Check for Certificate Revocation after Initial Check)
The software does not check the revocation status of a certificate after its initial revocation check, which can cause the software to perform privileged actions even after the certificate is revoked at a later time.
*Weakness ClassWeakness ClassNot Using Complete Mediation - (638)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 988 (SFP Secondary Cluster: Race Condition Window) > 638 (Not Using Complete Mediation)
The software does not perform access checks on a resource every time the resource is accessed by an entity, which can create resultant weaknesses if that entity's rights or privileges change over time.
*Weakness BaseWeakness BaseRace Condition Enabling Link Following - (363)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 988 (SFP Secondary Cluster: Race Condition Window) > 363 (Race Condition Enabling Link Following)
The software 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 software to access the wrong file.
*Weakness BaseWeakness BaseTime-of-check Time-of-use (TOCTOU) Race Condition - (367)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 988 (SFP Secondary Cluster: Race Condition Window) > 367 (Time-of-check Time-of-use (TOCTOU) Race Condition)
The software 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 software to perform invalid actions when the resource is in an unexpected state.TOCTTOUTOCCTOU
+CategoryCategorySFP Secondary Cluster: Unrestricted Lock - (989)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 989 (SFP Secondary Cluster: Unrestricted Lock)
This category identifies Software Fault Patterns (SFPs) within the Unrestricted Lock cluster.
*Weakness BaseWeakness BaseUnrestricted Externally Accessible Lock - (412)
888 (Software Fault Pattern (SFP) Clusters) > 894 (SFP Primary Cluster: Synchronization) > 989 (SFP Secondary Cluster: Unrestricted Lock) > 412 (Unrestricted Externally Accessible Lock)
The software 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.
+CategoryCategorySFP Primary Cluster: Tainted Input - (896)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input)
This category identifies Software Fault Patterns (SFPs) within the Tainted Input cluster.
+CategoryCategorySFP Secondary Cluster: Faulty Input Transformation - (992)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation)
This category identifies Software Fault Patterns (SFPs) within the Faulty Input Transformation cluster.
*Weakness BaseWeakness BaseCollapse of Data into Unsafe Value - (182)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 182 (Collapse of Data into Unsafe Value)
The software filters data in a way that causes it to be reduced or "collapsed" into an unsafe value that violates an expected security property.
*Weakness VariantWeakness VariantDouble Decoding of the Same Data - (174)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 174 (Double Decoding of the Same Data)
The software decodes the same input twice, which can limit the effectiveness of any protection mechanism that occurs in between the decoding operations.
*Weakness ClassWeakness ClassEncoding Error - (172)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 172 (Encoding Error)
The software does not properly encode or decode the data, resulting in unexpected values.
*Weakness ClassWeakness ClassImproper Encoding or Escaping of Output - (116)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 116 (Improper Encoding or Escaping of Output)
The software 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.Output SanitizationOutput ValidationOutput Encoding
*Weakness BaseWeakness BaseImproper Handling of Additional Special Element - (167)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 167 (Improper Handling of Additional Special Element)
The software receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is missing.
*Weakness VariantWeakness VariantImproper Handling of Alternate Encoding - (173)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 173 (Improper Handling of Alternate Encoding)
The software 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.
*Weakness BaseWeakness BaseImproper Handling of Case Sensitivity - (178)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 178 (Improper Handling of Case Sensitivity)
The software does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.
*Weakness BaseWeakness BaseImproper Handling of Inconsistent Special Elements - (168)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 168 (Improper Handling of Inconsistent Special Elements)
The software does not handle when an inconsistency exists between two or more special characters or reserved words.
*Weakness BaseWeakness BaseImproper Handling of Missing Special Element - (166)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 166 (Improper Handling of Missing Special Element)
The software receives input from an upstream component, but it does not handle or incorrectly handles when an expected special element is missing.
*Weakness VariantWeakness VariantImproper Handling of Mixed Encoding - (175)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 175 (Improper Handling of Mixed Encoding)
The software does not properly handle when the same input uses several different (mixed) encodings.
*Weakness VariantWeakness VariantImproper Handling of URL Encoding (Hex Encoding) - (177)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 177 (Improper Handling of URL Encoding (Hex Encoding))
The software does not properly handle when all or part of an input has been URL encoded.
*Weakness VariantWeakness VariantImproper Handling of Unicode Encoding - (176)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 176 (Improper Handling of Unicode Encoding)
The software does not properly handle when an input contains Unicode encoding.
*Weakness BaseWeakness BaseIncorrect Behavior Order: Early Validation - (179)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 179 (Incorrect Behavior Order: Early Validation)
The software 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.
*Weakness BaseWeakness BaseIncorrect Behavior Order: Validate Before Canonicalize - (180)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 180 (Incorrect Behavior Order: Validate Before Canonicalize)
The software validates input before it is canonicalized, which prevents the software from detecting data that becomes invalid after the canonicalization step.
*Weakness BaseWeakness BaseIncorrect Behavior Order: Validate Before Filter - (181)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 992 (SFP Secondary Cluster: Faulty Input Transformation) > 181 (Incorrect Behavior Order: Validate Before Filter)
The software validates data before it has been filtered, which prevents the software from detecting data that becomes invalid after the filtering step.Validate-before-cleanse
+CategoryCategorySFP Secondary Cluster: Incorrect Input Handling - (993)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling)
This category identifies Software Fault Patterns (SFPs) within the Incorrect Input Handling cluster.
*Weakness VariantWeakness VariantFailure to Handle Incomplete Element - (239)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 239 (Failure to Handle Incomplete Element)
The software does not properly handle when a particular element is not completely specified.
*Weakness VariantWeakness VariantFailure to Handle Missing Parameter - (234)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 234 (Failure to Handle Missing Parameter)
If too few arguments are sent to a function, the function will still pop the expected number of arguments from the stack. Potentially, a variable number of arguments could be exhausted in a function as well.
*Weakness VariantWeakness VariantImproper Handling of Extra Parameters - (235)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 235 (Improper Handling of Extra Parameters)
The software does not handle or incorrectly handles when the number of parameters, fields, or arguments with the same name exceeds the expected amount.
*Weakness VariantWeakness VariantImproper Handling of Extra Values - (231)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 231 (Improper Handling of Extra Values)
The software does not handle or incorrectly handles when more values are provided than expected.
*Weakness VariantWeakness VariantImproper Handling of Incomplete Structural Elements - (238)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 238 (Improper Handling of Incomplete Structural Elements)
The software does not handle or incorrectly handles when a particular structural element is not completely specified.
*Weakness VariantWeakness VariantImproper Handling of Inconsistent Structural Elements - (240)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 240 (Improper Handling of Inconsistent Structural Elements)
The software does not handle or incorrectly handles when two or more structural elements should be consistent, but are not.
*Weakness VariantWeakness VariantImproper Handling of Missing Values - (230)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 230 (Improper Handling of Missing Values)
The software 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.
*Weakness BaseWeakness BaseImproper Handling of Parameters - (233)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 233 (Improper Handling of Parameters)
The software does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined.
*Weakness BaseWeakness BaseImproper Handling of Structural Elements - (237)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 237 (Improper Handling of Structural Elements)
The software does not handle or incorrectly handles inputs that are related to complex structures.
*Weakness ClassWeakness ClassImproper Handling of Syntactically Invalid Structure - (228)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 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.
*Weakness VariantWeakness VariantImproper Handling of Undefined Parameters - (236)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 236 (Improper Handling of Undefined Parameters)
The software does not handle or incorrectly handles when a particular parameter, field, or argument name is not defined or supported by the product.
*Weakness VariantWeakness VariantImproper Handling of Undefined Values - (232)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 232 (Improper Handling of Undefined Values)
The software does not handle or incorrectly handles when a value is not defined or supported for the associated parameter, field, or argument name.
*Weakness BaseWeakness BaseImproper Handling of Unexpected Data Type - (241)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 241 (Improper Handling of Unexpected Data Type)
The software 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).
*Weakness BaseWeakness BaseImproper Handling of Values - (229)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 229 (Improper Handling of Values)
The software 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.
*Weakness BaseWeakness BaseImproper Validation of Integrity Check Value - (354)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 354 (Improper Validation of Integrity Check Value)
The software 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.
*Weakness BaseWeakness BaseInsufficient Type Distinction - (351)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 351 (Insufficient Type Distinction)
The software does not properly distinguish between different types of elements in a way that leads to insecure behavior.
*Weakness BaseWeakness BaseUse of Incorrect Byte Ordering - (198)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 993 (SFP Secondary Cluster: Incorrect Input Handling) > 198 (Use of Incorrect Byte Ordering)
The software receives input from an upstream component, but it does not account for byte ordering (e.g. big-endian and little-endian) when processing the input, causing an incorrect number or value to be used.
+CategoryCategorySFP Secondary Cluster: Tainted Input to Command - (990)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command)
This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Command cluster.
*Weakness VariantWeakness VariantASP.NET Misconfiguration: Not Using Input Validation Framework - (554)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 554 (ASP.NET Misconfiguration: Not Using Input Validation Framework)
The ASP.NET application does not use an input validation framework.
*Weakness BaseWeakness BaseArgument Injection or Modification - (88)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 88 (Argument Injection or Modification)
The software does not sufficiently delimit the arguments being passed to a component in another control sphere, allowing alternate arguments to be provided, leading to potentially security-relevant changes.
*Weakness VariantWeakness VariantCommand Shell in Externally Accessible Directory - (553)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 553 (Command Shell in Externally Accessible Directory)
A possible shell file exists in /cgi-bin/ or other accessible directories. This is extremely dangerous and can be used by an attacker to execute commands on the web server.
*Weakness BaseWeakness BaseDangling Database Cursor ('Cursor Injection') - (619)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 619 (Dangling Database Cursor ('Cursor Injection'))
If a database cursor is not closed properly, then it could become accessible to other users while retaining the same privileges that were originally assigned, leaving the cursor "dangling."
*Weakness VariantWeakness VariantDoubled Character XSS Manipulations - (85)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 85 (Doubled Character XSS Manipulations)
The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters.
*Weakness BaseWeakness BaseDynamic Variable Evaluation - (627)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 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.Dynamic evaluation
*Weakness BaseWeakness BaseExecutable Regular Expression Error - (624)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 624 (Executable Regular Expression Error)
The product uses a regular expression that either (1) contains an executable component with user-controlled inputs, or (2) allows a user to enable execution by inserting pattern modifiers.
*Weakness VariantWeakness VariantFailure to Sanitize Paired Delimiters - (157)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 157 (Failure to Sanitize Paired Delimiters)
The software does not properly handle the characters that are used to mark the beginning and ending of a group of entities, such as parentheses, brackets, and braces.
*Weakness ClassWeakness ClassFailure to Sanitize Special Element - (159)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 159 (Failure to Sanitize Special Element)
Weaknesses in this attack-focused category do not properly filter and interpret special elements in user-controlled input which could cause adverse effect on the software behavior and integrity.
*Weakness ClassWeakness ClassFailure to Sanitize Special Elements into a Different Plane (Special Element Injection) - (75)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 75 (Failure to Sanitize Special Elements into a Different Plane (Special Element Injection))
The software does not adequately filter user-controlled input for special elements with control implications.
*Weakness BaseWeakness BaseImproper Control of Resource Identifiers ('Resource Injection') - (99)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 99 (Improper Control of Resource Identifiers ('Resource Injection'))
The software 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.Insecure Direct Object Reference
*Weakness ClassWeakness ClassImproper Enforcement of Message or Data Structure - (707)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 707 (Improper Enforcement of Message or Data Structure)
The software does not enforce or incorrectly enforces that structured messages or data are well-formed before being read from an upstream component or sent to a downstream component.
*Weakness BaseWeakness BaseImproper Handling of Length Parameter Inconsistency - (130)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 130 (Improper Handling of Length Parameter Inconsistency )
The software 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.length manipulationlength tampering
*Weakness VariantWeakness VariantImproper Neutralization of Alternate XSS Syntax - (87)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 87 (Improper Neutralization of Alternate XSS Syntax)
The software does not neutralize or incorrectly neutralizes user-controlled input for alternate script syntax.
*Weakness BaseWeakness BaseImproper Neutralization of CRLF Sequences ('CRLF Injection') - (93)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 93 (Improper Neutralization of CRLF Sequences ('CRLF Injection'))
The software uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
*Weakness BaseWeakness BaseImproper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') - (113)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 113 (Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting'))
The software receives data from an upstream component, but does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.
*Weakness VariantWeakness VariantImproper Neutralization of Comment Delimiters - (151)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 151 (Improper Neutralization of Comment Delimiters)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as comment delimiters when they are sent to a downstream component.
*Weakness BaseWeakness BaseImproper Neutralization of Data within XPath Expressions ('XPath Injection') - (643)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 643 (Improper Neutralization of Data within XPath Expressions ('XPath Injection'))
The software 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.
*Weakness BaseWeakness BaseImproper Neutralization of Data within XQuery Expressions ('XQuery Injection') - (652)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 652 (Improper Neutralization of Data within XQuery Expressions ('XQuery Injection'))
The software uses external input to dynamically construct an XQuery 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.
*Weakness BaseWeakness BaseImproper Neutralization of Delimiters - (140)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 140 (Improper Neutralization of Delimiters)
The software does not neutralize or incorrectly neutralizes delimiters.
*Weakness BaseWeakness BaseImproper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') - (95)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 95 (Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection'))
The software 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").
*Weakness BaseWeakness BaseImproper Neutralization of Directives in Statically Saved Code ('Static Code Injection') - (96)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 96 (Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection'))
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Encoded URI Schemes in a Web Page - (84)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 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.
*Weakness BaseWeakness BaseImproper Neutralization of Equivalent Special Elements - (76)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 76 (Improper Neutralization of Equivalent Special Elements)
The software properly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.
*Weakness VariantWeakness VariantImproper Neutralization of Escape, Meta, or Control Sequences - (150)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 150 (Improper Neutralization of Escape, Meta, or Control Sequences)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Expression/Command Delimiters - (146)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 146 (Improper Neutralization of Expression/Command Delimiters)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of HTTP Headers for Scripting Syntax - (644)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 644 (Improper Neutralization of HTTP Headers for Scripting Syntax)
The application 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.
*Weakness BaseWeakness BaseImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') - (79)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'))
The software 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.XSSCSS
*Weakness VariantWeakness VariantImproper Neutralization of Input Leaders - (148)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 148 (Improper Neutralization of Input Leaders)
The application does not properly handle when a leading character or sequence ("leader") is missing or malformed, or if multiple leaders are used when only one should be allowed.
*Weakness VariantWeakness VariantImproper Neutralization of Input Terminators - (147)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 147 (Improper Neutralization of Input Terminators)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Internal Special Elements - (164)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 164 (Improper Neutralization of Internal Special Elements)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Invalid Characters in Identifiers in Web Pages - (86)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 86 (Improper Neutralization of Invalid Characters in Identifiers in Web Pages)
The software does not neutralize or incorrectly neutralizes invalid characters or byte sequences in the middle of tag names, URI schemes, and other identifiers.
*Weakness VariantWeakness VariantImproper Neutralization of Leading Special Elements - (160)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 160 (Improper Neutralization of Leading Special Elements)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes leading special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
*Weakness VariantWeakness VariantImproper Neutralization of Line Delimiters - (144)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 144 (Improper Neutralization of Line Delimiters)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Macro Symbols - (152)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 152 (Improper Neutralization of Macro Symbols)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as macro symbols when they are sent to a downstream component.
*Weakness VariantWeakness VariantImproper Neutralization of Multiple Internal Special Elements - (165)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 165 (Improper Neutralization of Multiple Internal Special Elements)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes multiple internal special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
*Weakness VariantWeakness VariantImproper Neutralization of Multiple Leading Special Elements - (161)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 161 (Improper Neutralization of Multiple Leading Special Elements)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes multiple leading special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
*Weakness VariantWeakness VariantImproper Neutralization of Multiple Trailing Special Elements - (163)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 163 (Improper Neutralization of Multiple Trailing Special Elements)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes multiple trailing special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
*Weakness VariantWeakness VariantImproper Neutralization of Null Byte or NUL Character - (158)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 158 (Improper Neutralization of Null Byte or NUL Character)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Parameter/Argument Delimiters - (141)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 141 (Improper Neutralization of Parameter/Argument Delimiters)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Quoting Syntax - (149)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 149 (Improper Neutralization of Quoting Syntax)
Quotes injected into an application 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.
*Weakness VariantWeakness VariantImproper Neutralization of Record Delimiters - (143)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 143 (Improper Neutralization of Record Delimiters)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as record delimiters when they are sent to a downstream component.
*Weakness VariantWeakness VariantImproper Neutralization of Script in Attributes in a Web Page - (83)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 83 (Improper Neutralization of Script in Attributes in a Web Page)
The software does not neutralize or incorrectly neutralizes "javascript:" or other URIs from dangerous attributes within tags, such as onmouseover, onload, onerror, or style.
*Weakness VariantWeakness VariantImproper Neutralization of Script in Attributes of IMG Tags in a Web Page - (82)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 82 (Improper Neutralization of Script in Attributes of IMG Tags in a Web Page)
The web application does not neutralize or incorrectly neutralizes scripting elements within attributes of HTML IMG tags, such as the src attribute.
*Weakness VariantWeakness VariantImproper Neutralization of Script in an Error Message Web Page - (81)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 81 (Improper Neutralization of Script in an Error Message Web Page)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) - (80)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 80 (Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS))
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Section Delimiters - (145)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 145 (Improper Neutralization of Section Delimiters)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as section delimiters when they are sent to a downstream component.
*Weakness VariantWeakness VariantImproper Neutralization of Server-Side Includes (SSI) Within a Web Page - (97)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 97 (Improper Neutralization of Server-Side Includes (SSI) Within a Web Page)
The software 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.
*Weakness ClassWeakness ClassImproper Neutralization of Special Elements - (138)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 138 (Improper Neutralization of Special Elements)
The software 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.
*Weakness ClassWeakness ClassImproper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') - (74)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'))
The software 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.
*Weakness ClassWeakness ClassImproper Neutralization of Special Elements used in a Command ('Command Injection') - (77)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 77 (Improper Neutralization of Special Elements used in a Command ('Command Injection'))
The software 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.
*Weakness BaseWeakness BaseImproper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') - (90)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 90 (Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection'))
The software 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.
*Weakness BaseWeakness BaseImproper Neutralization of Special Elements used in an OS Command ('OS Command Injection') - (78)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 78 (Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'))
The software 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.Shell injectionShell metacharacters
*Weakness BaseWeakness BaseImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') - (89)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 89 (Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'))
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Substitution Characters - (153)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 153 (Improper Neutralization of Substitution Characters)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as substitution characters when they are sent to a downstream component.
*Weakness VariantWeakness VariantImproper Neutralization of Trailing Special Elements - (162)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 162 (Improper Neutralization of Trailing Special Elements)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes trailing special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
*Weakness VariantWeakness VariantImproper Neutralization of Value Delimiters - (142)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 142 (Improper Neutralization of Value Delimiters)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Variable Name Delimiters - (154)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 154 (Improper Neutralization of Variable Name Delimiters)
The software 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.
*Weakness VariantWeakness VariantImproper Neutralization of Whitespace - (156)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 156 (Improper Neutralization of Whitespace)
The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as whitespace when they are sent to a downstream component.White space
*Weakness VariantWeakness VariantImproper Neutralization of Wildcards or Matching Symbols - (155)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 155 (Improper Neutralization of Wildcards or Matching Symbols)
The software 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.
*Weakness BaseWeakness BaseImproper Restriction of Names for Files and Other Resources - (641)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 641 (Improper Restriction of Names for Files and Other Resources)
The application constructs the name of a file or other resource using input from an upstream component, but does not restrict or incorrectly restricts the resulting name.
*Weakness VariantWeakness VariantImproper Restriction of XML External Entity Reference ('XXE') - (611)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 611 (Improper Restriction of XML External Entity Reference ('XXE'))
The software 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.XXE
*Weakness BaseWeakness BaseIncomplete Blacklist - (184)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 184 (Incomplete Blacklist)
An application uses a "blacklist" of prohibited values, but the blacklist is incomplete.
*Weakness BaseWeakness BaseInconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') - (444)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 444 (Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling'))
When malformed or abnormal HTTP requests are interpreted by one or more entities in the data flow between the user and the web server, such as a proxy or firewall, they can be interpreted inconsistently, allowing the attacker to "smuggle" a request to one device without the other device being aware of it.
*Weakness ClassWeakness ClassIncorrect Regular Expression - (185)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 185 (Incorrect Regular Expression)
The software specifies a regular expression in a way that causes data to be improperly matched or compared.
*Weakness BaseWeakness BaseMissing XML Validation - (112)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 112 (Missing XML Validation)
The software accepts XML from an untrusted source but does not validate the XML against the proper schema.
*Weakness VariantWeakness VariantNull Byte Interaction Error (Poison Null Byte) - (626)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 626 (Null Byte Interaction Error (Poison Null Byte))
The product does not properly handle null bytes or NUL characters when passing data between different representations or components.
*Weakness BaseWeakness BaseOverly Restrictive Regular Expression - (186)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 186 (Overly Restrictive Regular Expression)
A regular expression is overly restrictive, which prevents dangerous values from being detected.
*Weakness BaseWeakness BasePermissive Regular Expression - (625)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 625 (Permissive Regular Expression)
The product uses a regular expression that does not sufficiently restrict the set of allowed values.
*Weakness BaseWeakness BasePermissive Whitelist - (183)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 183 (Permissive Whitelist)
An application uses a "whitelist" of acceptable values, but the whitelist includes at least one unsafe value, leading to resultant weaknesses.
*Weakness VariantWeakness VariantReliance on File Name or Extension of Externally-Supplied File - (646)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 646 (Reliance on File Name or Extension of Externally-Supplied File)
The software 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.
*Weakness VariantWeakness VariantSQL Injection: Hibernate - (564)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 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.
*Weakness VariantWeakness VariantStruts: Duplicate Validation Forms - (102)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 102 (Struts: Duplicate Validation Forms)
The application uses multiple validation forms with the same name, which might cause the Struts Validator to validate a form that the programmer does not expect.
*Weakness VariantWeakness VariantStruts: Form Bean Does Not Extend Validation Class - (104)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 104 (Struts: Form Bean Does Not Extend Validation Class)
If a form bean does not extend an ActionForm subclass of the Validator framework, it can expose the application to other weaknesses related to insufficient input validation.
*Weakness VariantWeakness VariantStruts: Form Field Without Validator - (105)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 105 (Struts: Form Field Without Validator)
The application has a form field that is not validated by a corresponding validation form, which can introduce other weaknesses related to insufficient input validation.
*Weakness VariantWeakness VariantStruts: Incomplete validate() Method Definition - (103)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 103 (Struts: Incomplete validate() Method Definition)
The application has a validator form that either does not define a validate() method, or defines a validate() method but does not call super.validate().
*Weakness VariantWeakness VariantStruts: Plug-in Framework not in Use - (106)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 106 (Struts: Plug-in Framework not in Use)
When an application does not use an input validation framework such as the Struts Validator, there is a greater risk of introducing weaknesses related to insufficient input validation.
*Weakness VariantWeakness VariantStruts: Unused Validation Form - (107)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 107 (Struts: Unused Validation Form)
An unused validation form indicates that validation logic is not up-to-date.
*Weakness VariantWeakness VariantStruts: Unvalidated Action Form - (108)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 108 (Struts: Unvalidated Action Form)
Every Action Form must have a corresponding validation form.
*Weakness VariantWeakness VariantStruts: Validator Turned Off - (109)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 109 (Struts: Validator Turned Off)
Automatic filtering via a Struts bean has been turned off, which disables the Struts Validator and custom validation logic. This exposes the application to other weaknesses related to insufficient input validation.
*Weakness VariantWeakness VariantStruts: Validator Without Form Field - (110)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 110 (Struts: Validator Without Form Field)
Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.
*CategoryCategoryTechnology-Specific Input Validation Problems - (100)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 100 (Technology-Specific Input Validation Problems)
Weaknesses in this category are caused by inadequately implemented input validation within particular technologies.
*Weakness VariantWeakness VariantURL Redirection to Untrusted Site ('Open Redirect') - (601)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 601 (URL Redirection to Untrusted Site ('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.Open RedirectCross-site RedirectCross-domain Redirect
*Weakness BaseWeakness BaseUse of Externally-Controlled Format String - (134)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 134 (Use of Externally-Controlled Format String)
The software uses a function that accepts a format string as an argument, but the format string originates from an external source.
*Weakness BaseWeakness BaseVariable Extraction Error - (621)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 621 (Variable Extraction Error)
The product uses external input to determine the names of variables into which information is extracted, without verifying that the names of the specified variables are valid. This could cause the program to overwrite unintended variables.Variable overwrite
*Weakness BaseWeakness BaseXML Injection (aka Blind XPath Injection) - (91)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 990 (SFP Secondary Cluster: Tainted Input to Command) > 91 (XML Injection (aka Blind XPath Injection))
The software 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.
+CategoryCategorySFP Secondary Cluster: Tainted Input to Environment - (991)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment)
This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Environment cluster.
*Weakness BaseWeakness BaseDownload of Code Without Integrity Check - (494)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 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.
*Weakness BaseWeakness BaseExternal Control of Assumed-Immutable Web Parameter - (472)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 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.Assumed-Immutable Parameter Tampering
*Weakness ClassWeakness ClassExternal Influence of Sphere Definition - (673)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 673 (External Influence of Sphere Definition)
The product does not prevent the definition of control spheres from external actors.
*Weakness ClassWeakness ClassImproper Control of Generation of Code ('Code Injection') - (94)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 94 (Improper Control of Generation of Code ('Code Injection'))
The software 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.
*Weakness VariantWeakness VariantImproper Validation of Function Hook Arguments - (622)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 622 (Improper Validation of Function Hook Arguments)
A product adds hooks to user-accessible API functions, but does not properly validate the arguments. This could lead to resultant vulnerabilities.
*Weakness BaseWeakness BaseModification of Assumed-Immutable Data (MAID) - (471)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 471 (Modification of Assumed-Immutable Data (MAID))
The software does not properly protect an assumed-immutable element from being modified by an attacker.
*Weakness VariantWeakness VariantPHP External Variable Modification - (473)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 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.
*Weakness BaseWeakness BaseProcess Control - (114)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 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.
*Weakness BaseWeakness BaseUncontrolled Search Path Element - (427)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 427 (Uncontrolled Search Path Element)
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.DLL preloadingBinary plantingInsecure library loading
*Weakness VariantWeakness VariantUse of Dynamic Class Loading - (545)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 545 (Use of Dynamic Class Loading)
Dynamically loaded code has the potential to be malicious.
*Weakness BaseWeakness BaseUse of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') - (470)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 991 (SFP Secondary Cluster: Tainted Input to Environment) > 470 (Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection'))
The application uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.Reflection Injection
+CategoryCategorySFP Secondary Cluster: Tainted Input to Variable - (994)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 994 (SFP Secondary Cluster: Tainted Input to Variable)
This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Variable cluster.
*Weakness VariantWeakness VariantAuthorization Bypass Through User-Controlled SQL Primary Key - (566)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 994 (SFP Secondary Cluster: Tainted Input to Variable) > 566 (Authorization Bypass Through User-Controlled SQL Primary Key)
The software 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.
*Weakness VariantWeakness VariantDeserialization of Untrusted Data - (502)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 994 (SFP Secondary Cluster: Tainted Input to Variable) > 502 (Deserialization of Untrusted Data)
The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.Marshaling, UnmarshalingPickling, Unpickling
*Weakness BaseWeakness BaseExternal Control of System or Configuration Setting - (15)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 994 (SFP Secondary Cluster: Tainted Input to Variable) > 15 (External Control of System or Configuration Setting)
One or more system settings or configuration elements can be externally controlled by a user.
*Weakness BaseWeakness BaseExternal Initialization of Trusted Variables or Data Stores - (454)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 994 (SFP Secondary Cluster: Tainted Input to Variable) > 454 (External Initialization of Trusted Variables or Data Stores)
The software initializes critical internal variables or data stores using inputs that can be modified by untrusted actors.
*Weakness ClassWeakness ClassImproper Input Validation - (20)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 994 (SFP Secondary Cluster: Tainted Input to Variable) > 20 (Improper Input Validation)
The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.
*Weakness VariantWeakness VariantIncomplete Identification of Uploaded File Variables (PHP) - (616)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 994 (SFP Secondary Cluster: Tainted Input to Variable) > 616 (Incomplete Identification of Uploaded File Variables (PHP))
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.
*Weakness VariantWeakness VariantPublic Data Assigned to Private Array-Typed Field - (496)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 994 (SFP Secondary Cluster: Tainted Input to Variable) > 496 (Public Data Assigned to Private Array-Typed Field)
Assigning public data to a private array is equivalent to giving public access to the array.
*Weakness BaseWeakness BaseUnchecked Input for Loop Condition - (606)
888 (Software Fault Pattern (SFP) Clusters) > 896 (SFP Primary Cluster: Tainted Input) > 994 (SFP Secondary Cluster: Tainted Input to Variable) > 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 because of excessive looping.
+CategoryCategorySFP Primary Cluster: UI - (906)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI)
This category identifies Software Fault Patterns (SFPs) within the UI cluster.
+CategoryCategorySFP Secondary Cluster: Feature - (995)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 995 (SFP Secondary Cluster: Feature)
This category identifies Software Fault Patterns (SFPs) within the Feature cluster.
*Weakness BaseWeakness BaseInsufficient Psychological Acceptability - (655)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 995 (SFP Secondary Cluster: Feature) > 655 (Insufficient Psychological Acceptability)
The software 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.
*Weakness VariantWeakness VariantMissing Password Field Masking - (549)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 995 (SFP Secondary Cluster: Feature) > 549 (Missing Password Field Masking)
The software does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.
*Weakness BaseWeakness BaseMultiple Interpretations of UI Input - (450)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 995 (SFP Secondary Cluster: Feature) > 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.
*Weakness BaseWeakness BaseObsolete Feature in UI - (448)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 995 (SFP Secondary Cluster: Feature) > 448 (Obsolete Feature in UI)
A UI function is obsolete and the product does not warn the user.
*Weakness BaseWeakness BaseThe UI Performs the Wrong Action - (449)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 995 (SFP Secondary Cluster: Feature) > 449 (The UI Performs the Wrong Action)
The UI performs the wrong action with respect to the user's request.
*Weakness BaseWeakness BaseUnimplemented or Unsupported Feature in UI - (447)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 995 (SFP Secondary Cluster: Feature) > 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.
*Weakness BaseWeakness BaseUser Interface (UI) Misrepresentation of Critical Information - (451)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 995 (SFP Secondary Cluster: Feature) > 451 (User Interface (UI) Misrepresentation of Critical Information)
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.
+CategoryCategorySFP Secondary Cluster: Information Loss - (997)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 997 (SFP Secondary Cluster: Information Loss)
This category identifies Software Fault Patterns (SFPs) within the Information Loss cluster.
*Weakness ClassWeakness ClassInformation Loss or Omission - (221)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 997 (SFP Secondary Cluster: Information Loss) > 221 (Information Loss or Omission)
The software does not record, or improperly records, security-relevant information that leads to an incorrect decision or hampers later analysis.
*Weakness BaseWeakness BaseObscured Security-relevant Information by Alternate Name - (224)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 997 (SFP Secondary Cluster: Information Loss) > 224 (Obscured Security-relevant Information by Alternate Name)
The software records security-relevant information according to an alternate name of the affected entity, instead of the canonical name.
*Weakness BaseWeakness BaseOmission of Security-relevant Information - (223)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 997 (SFP Secondary Cluster: Information Loss) > 223 (Omission of Security-relevant Information)
The application 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.
*Weakness BaseWeakness BaseTruncation of Security-relevant Information - (222)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 997 (SFP Secondary Cluster: Information Loss) > 222 (Truncation of Security-relevant Information)
The application truncates the display, recording, or processing of security-relevant information in a way that can obscure the source or nature of an attack.
+CategoryCategorySFP Secondary Cluster: Security - (996)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 996 (SFP Secondary Cluster: Security)
This category identifies Software Fault Patterns (SFPs) within the Security cluster.
*Weakness BaseWeakness BaseInsufficient UI Warning of Dangerous Operations - (357)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 996 (SFP Secondary Cluster: Security) > 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.
*Weakness BaseWeakness BaseProduct UI does not Warn User of Unsafe Actions - (356)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 996 (SFP Secondary Cluster: Security) > 356 (Product UI does not Warn User of Unsafe Actions)
The software'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.
*Weakness BaseWeakness BaseUI Discrepancy for Security Feature - (446)
888 (Software Fault Pattern (SFP) Clusters) > 906 (SFP Primary Cluster: UI) > 996 (SFP Secondary Cluster: Security) > 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.
+CategoryCategorySFP Primary Cluster: Unused entities - (886)
888 (Software Fault Pattern (SFP) Clusters) > 886 (SFP Primary Cluster: Unused entities)
This category identifies Software Fault Patterns (SFPs) within the Unused entities cluster.
*Weakness VariantWeakness VariantAssignment to Variable without Use ('Unused Variable') - (563)
888 (Software Fault Pattern (SFP) Clusters) > 886 (SFP Primary Cluster: Unused entities) > 563 (Assignment to Variable without Use ('Unused Variable'))
The variable's value is assigned but never used, making it a dead store.
*Weakness VariantWeakness VariantComparing instead of Assigning - (482)
888 (Software Fault Pattern (SFP) Clusters) > 886 (SFP Primary Cluster: Unused entities) > 482 (Comparing instead of Assigning)
The code uses an operator for comparison when the intention was to perform an assignment.
*Weakness VariantWeakness VariantDead Code - (561)
888 (Software Fault Pattern (SFP) Clusters) > 886 (SFP Primary Cluster: Unused entities) > 561 (Dead Code)
The software contains dead code, which can never be executed.
Back to top