The Common Weakness Enumeration (CWE) List

 

Page content

All the Common Weakness Enumeration (CWE) list in a single page.

CWE is a catalog of vulnerabilities found in both software and hardware, created by the community. Its purpose is to provide a standardized vocabulary, establish a benchmark for security tools, and serve as a foundation for identifying, mitigating, and preventing weaknesses.

CWE-2: 7PK - Environment

  • Status: Draft
  • Weakness Abstractions: Category

This category has been deprecated. It was originally used for organizing weaknesses involving file names, which enabled access to files outside of a restricted directory (path traversal) or to perform operations on files that would otherwise be restricted (path equivalence). Consider using either the File Handling Issues category (CWE-1219) or the class Use of Incorrectly-Resolved Name or Reference (CWE-706).

More about CWE-2 definition and examples

CWE-5: J2EE Misconfiguration: Data Transmission Without Encryption

  • Status: Draft
  • Weakness Abstractions: Variant

Information sent over a network can be compromised while in transit. An attacker may be able to read or modify the contents if the data are sent in plaintext or are weakly encrypted.

More about CWE-5 definition and examples

Related CWE

CWE-6: J2EE Misconfiguration: Insufficient Session-ID Length

  • Status: Incomplete
  • Weakness Abstractions: Variant

The J2EE application is configured to use an insufficient session ID length.

More about CWE-6 definition and examples

Related CWE

CWE-7: J2EE Misconfiguration: Missing Custom Error Page

  • Status: Incomplete
  • Weakness Abstractions: Variant

The default error page of a web application should not display sensitive information about the software system.

More about CWE-7 definition and examples

Related CWE

CWE-8: J2EE Misconfiguration: Entity Bean Declared Remote

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-8 definition and examples

Related CWE

CWE-9: J2EE Misconfiguration: Weak Access Permissions for EJB Methods

  • Status: Draft
  • Weakness Abstractions: Variant

If elevated access rights are assigned to EJB methods, then an attacker can take advantage of the permissions to exploit the software system.

More about CWE-9 definition and examples

Related CWE

CWE-11: ASP.NET Misconfiguration: Creating Debug Binary

  • Status: Draft
  • Weakness Abstractions: Variant

Debugging messages help attackers learn about the system and plan a form of attack.

More about CWE-11 definition and examples

Related CWE

CWE-12: ASP.NET Misconfiguration: Missing Custom Error Page

  • Status: Draft
  • Weakness Abstractions: Variant

An ASP .NET application must enable custom error pages in order to prevent attackers from mining information from the framework’s built-in responses.

More about CWE-12 definition and examples

Related CWE

CWE-13: ASP.NET Misconfiguration: Password in Configuration File

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-13 definition and examples

Related CWE

CWE-14: Compiler Removal of Code to Clear Buffers

  • Status: Draft
  • Weakness Abstractions: Variant

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.”

More about CWE-14 definition and examples

Related CWE

CWE-15: External Control of System or Configuration Setting

  • Status: Incomplete
  • Weakness Abstractions: Base

One or more system settings or configuration elements can be externally controlled by a user.

More about CWE-15 definition and examples

Related CWE

CWE-16: Configuration

  • Status: Obsolete
  • Weakness Abstractions: Category

This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.

More about CWE-16 definition and examples

CWE-19: Data Processing Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are typically found in functionality that processes data. Data processing is the manipulation of input to retrieve or save information.

More about CWE-19 definition and examples

CWE-20: Improper Input Validation

  • Status: Stable
  • Weakness Abstractions: Class

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

More about CWE-20 definition and examples

Related CWE

CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)

  • Status: Stable
  • Weakness Abstractions: Base

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.

More about CWE-22 definition and examples

Related CWE

CWE-23: Relative Path Traversal

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-23 definition and examples

Related CWE

CWE-24: Path Traversal: ‘../filedir’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-24 definition and examples

Related CWE

CWE-25: Path Traversal: ‘/../filedir’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-25 definition and examples

Related CWE

CWE-26: Path Traversal: ‘/dir/../filename’

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-26 definition and examples

Related CWE

CWE-27: Path Traversal: ‘dir/../../filename’

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-27 definition and examples

Related CWE

CWE-28: Path Traversal: ‘..\filedir’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-28 definition and examples

Related CWE

CWE-29: Path Traversal: ‘..\filename’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-29 definition and examples

Related CWE

CWE-30: Path Traversal: ‘\dir..\filename’

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-30 definition and examples

Related CWE

CWE-31: Path Traversal: ‘dir....\filename’

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-31 definition and examples

Related CWE

CWE-32: Path Traversal: ‘…’ (Triple Dot)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-32 definition and examples

Related CWE

CWE-33: Path Traversal: ‘….’ (Multiple Dot)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-33 definition and examples

Related CWE

CWE-34: Path Traversal: ‘….//’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-34 definition and examples

Related CWE

CWE-35: Path Traversal: ‘…/…//’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-35 definition and examples

Related CWE

CWE-36: Absolute Path Traversal

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-36 definition and examples

Related CWE

CWE-37: Path Traversal: ‘/absolute/pathname/here’

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-37 definition and examples

Related CWE

CWE-38: Path Traversal: ‘\absolute\pathname\here’

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-38 definition and examples

Related CWE

CWE-39: Path Traversal: ‘C:dirname’

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-39 definition and examples

Related CWE

CWE-40: Path Traversal: ‘\UNC\share\name' (Windows UNC Share)

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-40 definition and examples

Related CWE

CWE-41: Improper Resolution of Path Equivalence

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-41 definition and examples

Related CWE

CWE-42: Path Equivalence: ‘filename.’ (Trailing Dot)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-42 definition and examples

Related CWE

CWE-43: Path Equivalence: ‘filename….’ (Multiple Trailing Dot)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-43 definition and examples

Related CWE

CWE-44: Path Equivalence: ‘file.name’ (Internal Dot)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-44 definition and examples

Related CWE

CWE-45: Path Equivalence: ‘file…name’ (Multiple Internal Dot)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-45 definition and examples

Related CWE

CWE-46: Path Equivalence: ‘filename ’ (Trailing Space)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-46 definition and examples

Related CWE

CWE-47: Path Equivalence: ’ filename’ (Leading Space)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-47 definition and examples

Related CWE

CWE-48: Path Equivalence: ‘file name’ (Internal Whitespace)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-48 definition and examples

Related CWE

CWE-49: Path Equivalence: ‘filename/’ (Trailing Slash)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-49 definition and examples

Related CWE

CWE-50: Path Equivalence: ‘//multiple/leading/slash’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-50 definition and examples

Related CWE

CWE-51: Path Equivalence: ‘/multiple//internal/slash’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-51 definition and examples

Related CWE

CWE-52: Path Equivalence: ‘/multiple/trailing/slash//’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-52 definition and examples

Related CWE

CWE-53: Path Equivalence: ‘\multiple\internal\backslash’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-53 definition and examples

Related CWE

CWE-54: Path Equivalence: ‘filedir' (Trailing Backslash)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-54 definition and examples

Related CWE

CWE-55: Path Equivalence: ‘/./’ (Single Dot Directory)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-55 definition and examples

Related CWE

CWE-56: Path Equivalence: ‘filedir*’ (Wildcard)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-56 definition and examples

Related CWE

CWE-57: Path Equivalence: ‘fakedir/../realdir/filename’

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-57 definition and examples

Related CWE

CWE-58: Path Equivalence: Windows 8.3 Filename

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-58 definition and examples

Related CWE

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-59 definition and examples

Related CWE

  • Status: Incomplete
  • Weakness Abstractions: Compound

The software, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the software to operate on unauthorized files.

More about CWE-61 definition and examples

Related CWE

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-62 definition and examples

Related CWE

CWE-64: Windows Shortcut Following (.LNK)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-64 definition and examples

Related CWE

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-65 definition and examples

Related CWE

CWE-66: Improper Handling of File Names that Identify Virtual Resources

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-66 definition and examples

Related CWE

CWE-67: Improper Handling of Windows Device Names

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-67 definition and examples

Related CWE

CWE-69: Improper Handling of Windows ::DATA Alternate Data Stream

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software does not properly prevent access to, or detect usage of, alternate data streams (ADS).

More about CWE-69 definition and examples

Related CWE

CWE-72: Improper Handling of Apple HFS+ Alternate Data Stream Path

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system.

More about CWE-72 definition and examples

Related CWE

CWE-73: External Control of File Name or Path

  • Status: Draft
  • Weakness Abstractions: Base

The software allows user input to control or influence paths or file names that are used in filesystem operations.

More about CWE-73 definition and examples

Related CWE

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component (‘Injection’)

  • Status: Incomplete
  • Weakness Abstractions: Class

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.

More about CWE-74 definition and examples

Related CWE

CWE-75: Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)

  • Status: Draft
  • Weakness Abstractions: Class

The software does not adequately filter user-controlled input for special elements with control implications.

More about CWE-75 definition and examples

Related CWE

CWE-76: Improper Neutralization of Equivalent Special Elements

  • Status: Draft
  • Weakness Abstractions: Base

The software properly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.

More about CWE-76 definition and examples

Related CWE

CWE-77: Improper Neutralization of Special Elements used in a Command (‘Command Injection’)

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-77 definition and examples

Related CWE

CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)

  • Status: Stable
  • Weakness Abstractions: Base

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.

More about CWE-78 definition and examples

Related CWE

CWE-79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)

  • Status: Stable
  • Weakness Abstractions: Base

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.

More about CWE-79 definition and examples

Related CWE

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-80 definition and examples

Related CWE

CWE-81: Improper Neutralization of Script in an Error Message Web Page

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-81 definition and examples

Related CWE

CWE-82: Improper Neutralization of Script in Attributes of IMG Tags in a Web Page

  • Status: Incomplete
  • Weakness Abstractions: Variant

The web application does not neutralize or incorrectly neutralizes scripting elements within attributes of HTML IMG tags, such as the src attribute.

More about CWE-82 definition and examples

Related CWE

CWE-83: Improper Neutralization of Script in Attributes in a Web Page

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not neutralize or incorrectly neutralizes “javascript:” or other URIs from dangerous attributes within tags, such as onmouseover, onload, onerror, or style.

More about CWE-83 definition and examples

Related CWE

CWE-84: Improper Neutralization of Encoded URI Schemes in a Web Page

  • Status: Draft
  • Weakness Abstractions: Variant

The web application improperly neutralizes user-controlled input for executable script disguised with URI encodings.

More about CWE-84 definition and examples

Related CWE

CWE-85: Doubled Character XSS Manipulations

  • Status: Draft
  • Weakness Abstractions: Variant

The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters.

More about CWE-85 definition and examples

Related CWE

CWE-86: Improper Neutralization of Invalid Characters in Identifiers in Web Pages

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not neutralize or incorrectly neutralizes invalid characters or byte sequences in the middle of tag names, URI schemes, and other identifiers.

More about CWE-86 definition and examples

Related CWE

CWE-87: Improper Neutralization of Alternate XSS Syntax

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not neutralize or incorrectly neutralizes user-controlled input for alternate script syntax.

More about CWE-87 definition and examples

Related CWE

CWE-88: Improper Neutralization of Argument Delimiters in a Command (‘Argument Injection’)

  • Status: Draft
  • Weakness Abstractions: Base

The software constructs a string for a command to executed by a separate componentin another control sphere, but it does not properly delimit theintended arguments, options, or switches within that command string.

More about CWE-88 definition and examples

Related CWE

CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)

  • Status: Stable
  • Weakness Abstractions: Base

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.

More about CWE-89 definition and examples

Related CWE

CWE-90: Improper Neutralization of Special Elements used in an LDAP Query (‘LDAP Injection’)

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-90 definition and examples

Related CWE

CWE-91: XML Injection (aka Blind XPath Injection)

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-91 definition and examples

Related CWE

CWE-93: Improper Neutralization of CRLF Sequences (‘CRLF Injection’)

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-93 definition and examples

Related CWE

CWE-94: Improper Control of Generation of Code (‘Code Injection’)

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-94 definition and examples

Related CWE

CWE-95: Improper Neutralization of Directives in Dynamically Evaluated Code (‘Eval Injection’)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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”).

More about CWE-95 definition and examples

Related CWE

CWE-96: Improper Neutralization of Directives in Statically Saved Code (‘Static Code Injection’)

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-96 definition and examples

Related CWE

CWE-97: Improper Neutralization of Server-Side Includes (SSI) Within a Web Page

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-97 definition and examples

Related CWE

CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program (‘PHP Remote File Inclusion’)

  • Status: Draft
  • Weakness Abstractions: Variant

The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in “require,” “include,” or similar functions.

More about CWE-98 definition and examples

Related CWE

CWE-99: Improper Control of Resource Identifiers (‘Resource Injection’)

  • Status: Draft
  • Weakness Abstractions: Class

This category has been deprecated. It was originally intended as a “catch-all” for input validation problems in technologies that did not have their own CWE, but introduces unnecessary depth to the hierarchy.

More about CWE-99 definition and examples

Related CWE

CWE-102: Struts: Duplicate Validation Forms

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-102 definition and examples

Related CWE

CWE-103: Struts: Incomplete validate() Method Definition

  • Status: Draft
  • Weakness Abstractions: Variant

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().

More about CWE-103 definition and examples

Related CWE

CWE-104: Struts: Form Bean Does Not Extend Validation Class

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-104 definition and examples

Related CWE

CWE-105: Struts: Form Field Without Validator

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-105 definition and examples

Related CWE

CWE-106: Struts: Plug-in Framework not in Use

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-106 definition and examples

Related CWE

CWE-107: Struts: Unused Validation Form

  • Status: Draft
  • Weakness Abstractions: Variant

An unused validation form indicates that validation logic is not up-to-date.

More about CWE-107 definition and examples

Related CWE

CWE-108: Struts: Unvalidated Action Form

  • Status: Incomplete
  • Weakness Abstractions: Variant

Every Action Form must have a corresponding validation form.

More about CWE-108 definition and examples

Related CWE

CWE-109: Struts: Validator Turned Off

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-109 definition and examples

Related CWE

CWE-110: Struts: Validator Without Form Field

  • Status: Draft
  • Weakness Abstractions: Variant

Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.

More about CWE-110 definition and examples

Related CWE

CWE-111: Direct Use of Unsafe JNI

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-111 definition and examples

Related CWE

CWE-112: Missing XML Validation

  • Status: Draft
  • Weakness Abstractions: Base

The software accepts XML from an untrusted source but does not validate the XML against the proper schema.

More about CWE-112 definition and examples

Related CWE

CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers (‘HTTP Response Splitting’)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-113 definition and examples

Related CWE

CWE-114: Process Control

  • Status: Incomplete
  • Weakness Abstractions: Class

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.

More about CWE-114 definition and examples

Related CWE

CWE-115: Misinterpretation of Input

  • Status: Incomplete
  • Weakness Abstractions: Base

The software misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.

More about CWE-115 definition and examples

Related CWE

CWE-116: Improper Encoding or Escaping of Output

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-116 definition and examples

Related CWE

CWE-117: Improper Output Neutralization for Logs

  • Status: Draft
  • Weakness Abstractions: Base

The software does not neutralize or incorrectly neutralizes output that is written to logs.

More about CWE-117 definition and examples

Related CWE

CWE-118: Incorrect Access of Indexable Resource (‘Range Error’)

  • Status: Incomplete
  • Weakness Abstractions: Class

This entry has been deprecated because it was a duplicate of CWE-908. All content has been transferred to CWE-908.

More about CWE-118 definition and examples

Related CWE

CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer

  • Status: Stable
  • Weakness Abstractions: Class

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.

More about CWE-119 definition and examples

Related CWE

CWE-120: Buffer Copy without Checking Size of Input (‘Classic Buffer Overflow’)

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-120 definition and examples

Related CWE

CWE-121: Stack-based Buffer Overflow

  • Status: Draft
  • Weakness Abstractions: Variant

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).

More about CWE-121 definition and examples

Related CWE

CWE-122: Heap-based Buffer Overflow

  • Status: Draft
  • Weakness Abstractions: Variant

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().

More about CWE-122 definition and examples

Related CWE

CWE-123: Write-what-where Condition

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-123 definition and examples

Related CWE

CWE-124: Buffer Underwrite (‘Buffer Underflow’)

  • Status: Incomplete
  • Weakness Abstractions: Base

The software writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.

More about CWE-124 definition and examples

Related CWE

CWE-125: Out-of-bounds Read

  • Status: Draft
  • Weakness Abstractions: Base

The software reads data past the end, or before the beginning, of the intended buffer.

More about CWE-125 definition and examples

Related CWE

CWE-126: Buffer Over-read

  • Status: Draft
  • Weakness Abstractions: Variant

The software reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.

More about CWE-126 definition and examples

Related CWE

CWE-127: Buffer Under-read

  • Status: Draft
  • Weakness Abstractions: Variant

The software reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations prior to the targeted buffer.

More about CWE-127 definition and examples

Related CWE

CWE-128: Wrap-around Error

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-128 definition and examples

Related CWE

CWE-129: Improper Validation of Array Index

  • Status: Draft
  • Weakness Abstractions: Variant

The most common condition situation leading to an out-of-bounds array index is the use of loop index variables as buffer indexes. If the end condition for the loop is subject to a flaw, the index can grow or shrink unbounded, therefore causing a buffer overflow or underflow. Another common situation leading to this condition is the use of a function’s return value, or the resulting value of a calculation directly as an index in to a buffer.

More about CWE-129 definition and examples

Related CWE

CWE-130: Improper Handling of Length Parameter Inconsistency

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-130 definition and examples

Related CWE

CWE-131: Incorrect Calculation of Buffer Size

  • Status: Draft
  • Weakness Abstractions: Base

The software does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.

More about CWE-131 definition and examples

Related CWE

CWE-133: String Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the creation and modification of strings.

More about CWE-133 definition and examples

CWE-134: Use of Externally-Controlled Format String

  • Status: Draft
  • Weakness Abstractions: Base

The software uses a function that accepts a format string as an argument, but the format string originates from an external source.

More about CWE-134 definition and examples

Related CWE

CWE-135: Incorrect Calculation of Multi-Byte String Length

  • Status: Draft
  • Weakness Abstractions: Base

The software does not correctly calculate the length of strings that can contain wide or multi-byte characters.

More about CWE-135 definition and examples

Related CWE

CWE-136: Type Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are caused by improper data type transformation or improper handling of multiple data types.

More about CWE-136 definition and examples

CWE-137: Data Neutralization Issues

  • Status: Draft
  • Weakness Abstractions: Category

This entry has been deprecated. It is a leftover from PLOVER, but CWE-138 is a more appropriate mapping.

More about CWE-137 definition and examples

CWE-138: Improper Neutralization of Special Elements

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-138 definition and examples

Related CWE

CWE-140: Improper Neutralization of Delimiters

  • Status: Draft
  • Weakness Abstractions: Base

The software does not neutralize or incorrectly neutralizes delimiters.

More about CWE-140 definition and examples

Related CWE

CWE-141: Improper Neutralization of Parameter/Argument Delimiters

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-141 definition and examples

Related CWE

CWE-142: Improper Neutralization of Value Delimiters

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-142 definition and examples

Related CWE

CWE-143: Improper Neutralization of Record Delimiters

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-143 definition and examples

Related CWE

CWE-144: Improper Neutralization of Line Delimiters

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-144 definition and examples

Related CWE

CWE-145: Improper Neutralization of Section Delimiters

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-145 definition and examples

Related CWE

CWE-146: Improper Neutralization of Expression/Command Delimiters

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-146 definition and examples

Related CWE

CWE-147: Improper Neutralization of Input Terminators

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-147 definition and examples

Related CWE

CWE-148: Improper Neutralization of Input Leaders

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-148 definition and examples

Related CWE

CWE-149: Improper Neutralization of Quoting Syntax

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-149 definition and examples

Related CWE

CWE-150: Improper Neutralization of Escape, Meta, or Control Sequences

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-150 definition and examples

Related CWE

CWE-151: Improper Neutralization of Comment Delimiters

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-151 definition and examples

Related CWE

CWE-152: Improper Neutralization of Macro Symbols

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-152 definition and examples

Related CWE

CWE-153: Improper Neutralization of Substitution Characters

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-153 definition and examples

Related CWE

CWE-154: Improper Neutralization of Variable Name Delimiters

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-154 definition and examples

Related CWE

CWE-155: Improper Neutralization of Wildcards or Matching Symbols

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-155 definition and examples

Related CWE

CWE-156: Improper Neutralization of Whitespace

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-156 definition and examples

Related CWE

CWE-157: Failure to Sanitize Paired Delimiters

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-157 definition and examples

Related CWE

CWE-158: Improper Neutralization of Null Byte or NUL Character

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-158 definition and examples

Related CWE

CWE-159: Improper Handling of Invalid Use of Special Elements

  • Status: Draft
  • Weakness Abstractions: Class

The product does not properly filter, remove, quote, or otherwise manage the invalid use of special elements in user-controlled input, which could cause adverse effect on its behavior and integrity.

More about CWE-159 definition and examples

Related CWE

CWE-160: Improper Neutralization of Leading Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-160 definition and examples

Related CWE

CWE-161: Improper Neutralization of Multiple Leading Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-161 definition and examples

Related CWE

CWE-162: Improper Neutralization of Trailing Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-162 definition and examples

Related CWE

CWE-163: Improper Neutralization of Multiple Trailing Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-163 definition and examples

Related CWE

CWE-164: Improper Neutralization of Internal Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-164 definition and examples

Related CWE

CWE-165: Improper Neutralization of Multiple Internal Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-165 definition and examples

Related CWE

CWE-166: Improper Handling of Missing Special Element

  • Status: Draft
  • Weakness Abstractions: Base

The software receives input from an upstream component, but it does not handle or incorrectly handles when an expected special element is missing.

More about CWE-166 definition and examples

Related CWE

CWE-167: Improper Handling of Additional Special Element

  • Status: Draft
  • Weakness Abstractions: Base

The software receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided.

More about CWE-167 definition and examples

Related CWE

CWE-168: Improper Handling of Inconsistent Special Elements

  • Status: Draft
  • Weakness Abstractions: Base

The software does not properly handle input in which an inconsistency exists between two or more special characters or reserved words.

More about CWE-168 definition and examples

Related CWE

CWE-170: Improper Null Termination

  • Status: Incomplete
  • Weakness Abstractions: Base

The software does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator.

More about CWE-170 definition and examples

Related CWE

CWE-172: Encoding Error

  • Status: Draft
  • Weakness Abstractions: Class

The software does not properly encode or decode the data, resulting in unexpected values.

More about CWE-172 definition and examples

Related CWE

CWE-173: Improper Handling of Alternate Encoding

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-173 definition and examples

Related CWE

CWE-174: Double Decoding of the Same Data

  • Status: Draft
  • Weakness Abstractions: Variant

The software decodes the same input twice, which can limit the effectiveness of any protection mechanism that occurs in between the decoding operations.

More about CWE-174 definition and examples

Related CWE

CWE-175: Improper Handling of Mixed Encoding

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not properly handle when the same input uses several different (mixed) encodings.

More about CWE-175 definition and examples

Related CWE

CWE-176: Improper Handling of Unicode Encoding

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not properly handle when an input contains Unicode encoding.

More about CWE-176 definition and examples

Related CWE

CWE-177: Improper Handling of URL Encoding (Hex Encoding)

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not properly handle when all or part of an input has been URL encoded.

More about CWE-177 definition and examples

Related CWE

CWE-178: Improper Handling of Case Sensitivity

  • Status: Incomplete
  • Weakness Abstractions: Base

The software does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.

More about CWE-178 definition and examples

Related CWE

CWE-179: Incorrect Behavior Order: Early Validation

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-179 definition and examples

Related CWE

CWE-180: Incorrect Behavior Order: Validate Before Canonicalize

  • Status: Draft
  • Weakness Abstractions: Variant

The software validates input before it is canonicalized, which prevents the software from detecting data that becomes invalid after the canonicalization step.

More about CWE-180 definition and examples

Related CWE

CWE-181: Incorrect Behavior Order: Validate Before Filter

  • Status: Draft
  • Weakness Abstractions: Variant

The software validates data before it has been filtered, which prevents the software from detecting data that becomes invalid after the filtering step.

More about CWE-181 definition and examples

Related CWE

CWE-182: Collapse of Data into Unsafe Value

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-182 definition and examples

Related CWE

CWE-183: Permissive List of Allowed Inputs

  • Status: Draft
  • Weakness Abstractions: Base

The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.

More about CWE-183 definition and examples

Related CWE

CWE-184: Incomplete List of Disallowed Inputs

  • Status: Draft
  • Weakness Abstractions: Base

The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete, leading to resultant weaknesses.

More about CWE-184 definition and examples

Related CWE

CWE-185: Incorrect Regular Expression

  • Status: Draft
  • Weakness Abstractions: Class

The software specifies a regular expression in a way that causes data to be improperly matched or compared.

More about CWE-185 definition and examples

Related CWE

CWE-186: Overly Restrictive Regular Expression

  • Status: Draft
  • Weakness Abstractions: Base

A regular expression is overly restrictive, which prevents dangerous values from being detected.

More about CWE-186 definition and examples

Related CWE

CWE-187: Partial String Comparison

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-187 definition and examples

Related CWE

CWE-188: Reliance on Data/Memory Layout

  • Status: Draft
  • Weakness Abstractions: Base

The software makes invalid assumptions about how protocol data or memory is organized at a lower level, resulting in unintended program behavior.

More about CWE-188 definition and examples

Related CWE

CWE-189: Numeric Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to improper calculation or conversion of numbers.

More about CWE-189 definition and examples

CWE-190: Integer Overflow or Wraparound

  • Status: Stable
  • Weakness Abstractions: Base

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.

More about CWE-190 definition and examples

Related CWE

CWE-191: Integer Underflow (Wrap or Wraparound)

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-191 definition and examples

Related CWE

CWE-192: Integer Coercion Error

  • Status: Incomplete
  • Weakness Abstractions: Variant

Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types.

More about CWE-192 definition and examples

Related CWE

CWE-193: Off-by-one Error

  • Status: Draft
  • Weakness Abstractions: Base

A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.

More about CWE-193 definition and examples

Related CWE

CWE-194: Unexpected Sign Extension

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-194 definition and examples

Related CWE

CWE-195: Signed to Unsigned Conversion Error

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-195 definition and examples

Related CWE

CWE-196: Unsigned to Signed Conversion Error

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-196 definition and examples

Related CWE

CWE-197: Numeric Truncation Error

  • Status: Incomplete
  • Weakness Abstractions: Base

Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.

More about CWE-197 definition and examples

Related CWE

CWE-198: Use of Incorrect Byte Ordering

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-198 definition and examples

Related CWE

CWE-199: Information Management Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to improper handling of sensitive information.

More about CWE-199 definition and examples

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

  • Status: Draft
  • Weakness Abstractions: Class

Separate mistakes or weaknesses could inadvertently make the sensitive information available to an attacker, such as in a detailed error message that can be read by an unauthorized party

More about CWE-200 definition and examples

Related CWE

CWE-201: Insertion of Sensitive Information Into Sent Data

  • Status: Draft
  • Weakness Abstractions: Base

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

More about CWE-201 definition and examples

Related CWE

CWE-202: Exposure of Sensitive Information Through Data Queries

  • Status: Draft
  • Weakness Abstractions: Variant

When trying to keep information confidential, an attacker can often infer some of the information by using statistics.

More about CWE-202 definition and examples

Related CWE

CWE-203: Observable Discrepancy

  • Status: Incomplete
  • Weakness Abstractions: Base

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.

More about CWE-203 definition and examples

Related CWE

CWE-204: Observable Response Discrepancy

  • Status: Incomplete
  • Weakness Abstractions: Base

The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.

More about CWE-204 definition and examples

Related CWE

CWE-205: Observable Behavioral Discrepancy

  • Status: Incomplete
  • Weakness Abstractions: Base

The product’s behaviors indicate important differences that may be observed by unauthorized actors in a way that reveals (1) its internal state or decision process, or (2) differences from other products with equivalent functionality.

More about CWE-205 definition and examples

Related CWE

CWE-206: Observable Internal Behavioral Discrepancy

  • Status: Incomplete
  • Weakness Abstractions: Variant

The product performs multiple behaviors that are combined to produce a single result, but the individual behaviors are observable separately in a way that allows attackers to reveal internal state or internal decision points.

More about CWE-206 definition and examples

Related CWE

CWE-207: Observable Behavioral Discrepancy With Equivalent Products

  • Status: Draft
  • Weakness Abstractions: Variant

The product operates in an environment in which its existence or specific identity should not be known, but it behaves differently than other products with equivalent functionality, in a way that is observable to an attacker.

More about CWE-207 definition and examples

Related CWE

CWE-208: Observable Timing Discrepancy

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-208 definition and examples

Related CWE

CWE-209: Generation of Error Message Containing Sensitive Information

  • Status: Draft
  • Weakness Abstractions: Base

The software generates an error message that includes sensitive information about its environment, users, or associated data.

More about CWE-209 definition and examples

Related CWE

CWE-210: Self-generated Error Message Containing Sensitive Information

  • Status: Draft
  • Weakness Abstractions: Base

The software identifies an error condition and creates its own diagnostic or error messages that contain sensitive information.

More about CWE-210 definition and examples

Related CWE

CWE-211: Externally-Generated Error Message Containing Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Base

The application performs an operation that triggers an external diagnostic or error message that is not directly generated or controlled by the application, such as an error generated by the programming language interpreter that the software uses. The error can contain sensitive system information.

More about CWE-211 definition and examples

Related CWE

CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer

  • Status: Incomplete
  • Weakness Abstractions: Base

The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.

More about CWE-212 definition and examples

Related CWE

CWE-213: Exposure of Sensitive Information Due to Incompatible Policies

  • Status: Draft
  • Weakness Abstractions: Base

The product’s intended functionality exposes information to certain actors in accordance with the developer’s security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product’s administrator, users, or others whose information is being processed.

More about CWE-213 definition and examples

Related CWE

CWE-214: Invocation of Process Using Visible Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Base

A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system.

More about CWE-214 definition and examples

Related CWE

CWE-215: Insertion of Sensitive Information Into Debugging Code

  • Status: Draft
  • Weakness Abstractions: Base

This weakness has been deprecated because it was a duplicate of CWE-493. All content has been transferred to CWE-493.

More about CWE-215 definition and examples

Related CWE

CWE-219: Storage of File with Sensitive Data Under Web Root

  • Status: Draft
  • Weakness Abstractions: Variant

The application stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.

More about CWE-219 definition and examples

Related CWE

CWE-220: Storage of File With Sensitive Data Under FTP Root

  • Status: Draft
  • Weakness Abstractions: Variant

The application stores sensitive data under the FTP server root with insufficient access control, which might make it accessible to untrusted parties.

More about CWE-220 definition and examples

Related CWE

CWE-221: Information Loss or Omission

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not record, or improperly records, security-relevant information that leads to an incorrect decision or hampers later analysis.

More about CWE-221 definition and examples

Related CWE

CWE-222: Truncation of Security-relevant Information

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-222 definition and examples

Related CWE

CWE-223: Omission of Security-relevant Information

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-223 definition and examples

Related CWE

CWE-224: Obscured Security-relevant Information by Alternate Name

  • Status: Incomplete
  • Weakness Abstractions: Base

This weakness can be found at CWE-199.

More about CWE-224 definition and examples

Related CWE

CWE-226: Sensitive Information in Resource Not Removed Before Reuse

  • Status: Draft
  • Weakness Abstractions: Base

When a device releases a resource such as memory or a file for reuse by other entities, information contained in the resource is not fully cleared prior to reuse of the resource.

More about CWE-226 definition and examples

Related CWE

CWE-227: 7PK - API Abuse

  • Status: Draft
  • Weakness Abstractions: Category

This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that involve the software using an API in a manner contrary to its intended use. According to the authors of the Seven Pernicious Kingdoms, “An API is a contract between a caller and a callee. The most common forms of API misuse occurs when the caller does not honor its end of this contract. For example, if a program does not call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller misuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated.”

More about CWE-227 definition and examples

CWE-228: Improper Handling of Syntactically Invalid Structure

  • Status: Incomplete
  • Weakness Abstractions: Class

The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification.

More about CWE-228 definition and examples

Related CWE

CWE-229: Improper Handling of Values

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-229 definition and examples

Related CWE

CWE-230: Improper Handling of Missing Values

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-230 definition and examples

Related CWE

CWE-231: Improper Handling of Extra Values

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not handle or incorrectly handles when more values are provided than expected.

More about CWE-231 definition and examples

Related CWE

CWE-232: Improper Handling of Undefined Values

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not handle or incorrectly handles when a value is not defined or supported for the associated parameter, field, or argument name.

More about CWE-232 definition and examples

Related CWE

CWE-233: Improper Handling of Parameters

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-233 definition and examples

Related CWE

CWE-234: Failure to Handle Missing Parameter

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-234 definition and examples

Related CWE

CWE-235: Improper Handling of Extra Parameters

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not handle or incorrectly handles when the number of parameters, fields, or arguments with the same name exceeds the expected amount.

More about CWE-235 definition and examples

Related CWE

CWE-236: Improper Handling of Undefined Parameters

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not handle or incorrectly handles when a particular parameter, field, or argument name is not defined or supported by the product.

More about CWE-236 definition and examples

Related CWE

CWE-237: Improper Handling of Structural Elements

  • Status: Incomplete
  • Weakness Abstractions: Base

The software does not handle or incorrectly handles inputs that are related to complex structures.

More about CWE-237 definition and examples

Related CWE

CWE-238: Improper Handling of Incomplete Structural Elements

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not handle or incorrectly handles when a particular structural element is not completely specified.

More about CWE-238 definition and examples

Related CWE

CWE-239: Failure to Handle Incomplete Element

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not properly handle when a particular element is not completely specified.

More about CWE-239 definition and examples

Related CWE

CWE-240: Improper Handling of Inconsistent Structural Elements

  • Status: Draft
  • Weakness Abstractions: Base

The software does not handle or incorrectly handles when two or more structural elements should be consistent, but are not.

More about CWE-240 definition and examples

Related CWE

CWE-241: Improper Handling of Unexpected Data Type

  • Status: Draft
  • Weakness Abstractions: Base

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).

More about CWE-241 definition and examples

Related CWE

CWE-242: Use of Inherently Dangerous Function

  • Status: Draft
  • Weakness Abstractions: Base

The program calls a function that can never be guaranteed to work safely.

More about CWE-242 definition and examples

Related CWE

CWE-243: Creation of chroot Jail Without Changing Working Directory

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-243 definition and examples

Related CWE

CWE-244: Improper Clearing of Heap Memory Before Release (‘Heap Inspection’)

  • Status: Draft
  • Weakness Abstractions: Variant

Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory.

More about CWE-244 definition and examples

Related CWE

CWE-245: J2EE Bad Practices: Direct Management of Connections

  • Status: Draft
  • Weakness Abstractions: Variant

The J2EE application directly manages connections, instead of using the container’s connection management facilities.

More about CWE-245 definition and examples

Related CWE

CWE-246: J2EE Bad Practices: Direct Use of Sockets

  • Status: Draft
  • Weakness Abstractions: Variant

This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350.

More about CWE-246 definition and examples

Related CWE

CWE-248: Uncaught Exception

  • Status: Draft
  • Weakness Abstractions: Base

This entry has been deprecated because of name confusion and an accidental combination of multiple weaknesses. Most of its content has been transferred to CWE-785. This entry was deprecated for several reasons. The primary reason is over-loading of the “path manipulation” term and the description. The original description for this entry was the same as that for the “Often Misused: File System” item in the original Seven Pernicious Kingdoms paper. However, Seven Pernicious Kingdoms also has a “Path Manipulation” phrase that is for external control of pathnames (CWE-73), which is a factor in symbolic link following and path traversal, neither of which is explicitly mentioned in 7PK. Fortify uses the phrase “Often Misused: Path Manipulation” for a broader range of problems, generally for issues related to buffer management. Given the multiple conflicting uses of this term, there is a chance that CWE users may have incorrectly mapped to this entry. The second reason for deprecation is an implied combination of multiple weaknesses within buffer-handling functions. The focus of this entry was generally on the path-conversion functions and their association with buffer overflows. However, some of Fortify’s Vulncat entries have the term “path manipulation” but describe a non-overflow weakness in which the buffer is not guaranteed to contain the entire pathname, i.e., there is information truncation (see CWE-222 for a similar concept). A new entry for this non-overflow weakness may be created in a future version of CWE.

More about CWE-248 definition and examples

Related CWE

CWE-250: Execution with Unnecessary Privileges

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-250 definition and examples

Related CWE

CWE-251: Often Misused: String Management

  • Status: Incomplete
  • Weakness Abstractions: Category

Functions that manipulate strings encourage buffer overflows.

More about CWE-251 definition and examples

CWE-252: Unchecked Return Value

  • Status: Draft
  • Weakness Abstractions: Base

The software does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions.

More about CWE-252 definition and examples

Related CWE

CWE-253: Incorrect Check of Function Return Value

  • Status: Incomplete
  • Weakness Abstractions: Base

The software incorrectly checks a return value from a function, which prevents the software from detecting errors or exceptional conditions.

More about CWE-253 definition and examples

Related CWE

CWE-254: 7PK - Security Features

  • Status: Incomplete
  • Weakness Abstractions: Category

Software security is not security software. Here we’re concerned with topics like authentication, access control, confidentiality, cryptography, and privilege management.

More about CWE-254 definition and examples

CWE-255: Credentials Management Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the management of credentials.

More about CWE-255 definition and examples

CWE-256: Unprotected Storage of Credentials

  • Status: Incomplete
  • Weakness Abstractions: Base

Storing a password in plaintext may result in a system compromise.

More about CWE-256 definition and examples

Related CWE

CWE-257: Storing Passwords in a Recoverable Format

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-257 definition and examples

Related CWE

CWE-258: Empty Password in Configuration File

  • Status: Incomplete
  • Weakness Abstractions: Variant

Using an empty string as a password is insecure.

More about CWE-258 definition and examples

Related CWE

CWE-259: Use of Hard-coded Password

  • Status: Draft
  • Weakness Abstractions: Variant

The software contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.

More about CWE-259 definition and examples

Related CWE

CWE-260: Password in Configuration File

  • Status: Incomplete
  • Weakness Abstractions: Base

The software stores a password in a configuration file that might be accessible to actors who do not know the password.

More about CWE-260 definition and examples

Related CWE

CWE-261: Weak Encoding for Password

  • Status: Incomplete
  • Weakness Abstractions: Base

Obscuring a password with a trivial encoding does not protect the password.

More about CWE-261 definition and examples

Related CWE

CWE-262: Not Using Password Aging

  • Status: Draft
  • Weakness Abstractions: Base

If no mechanism is in place for managing password aging, users will have no incentive to update passwords in a timely manner.

More about CWE-262 definition and examples

Related CWE

CWE-263: Password Aging with Long Expiration

  • Status: Draft
  • Weakness Abstractions: Base

Allowing password aging to occur unchecked can result in the possibility of diminished password integrity.

More about CWE-263 definition and examples

Related CWE

CWE-264: Permissions, Privileges, and Access Controls

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.

More about CWE-264 definition and examples

CWE-265: Privilege Issues

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category occur with improper handling, assignment, or management of privileges. A privilege is a property of an agent, such as a user. It lets the agent do things that are not ordinarily allowed. For example, there are privileges which allow an agent to perform maintenance functions such as restart a computer.

More about CWE-265 definition and examples

CWE-266: Incorrect Privilege Assignment

  • Status: Draft
  • Weakness Abstractions: Base

A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

More about CWE-266 definition and examples

Related CWE

CWE-267: Privilege Defined With Unsafe Actions

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-267 definition and examples

Related CWE

CWE-268: Privilege Chaining

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-268 definition and examples

Related CWE

CWE-269: Improper Privilege Management

  • Status: Draft
  • Weakness Abstractions: Class

The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

More about CWE-269 definition and examples

Related CWE

CWE-270: Privilege Context Switching Error

  • Status: Draft
  • Weakness Abstractions: Base

The software does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.

More about CWE-270 definition and examples

Related CWE

CWE-271: Privilege Dropping / Lowering Errors

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not drop privileges before passing control of a resource to an actor that does not have those privileges.

More about CWE-271 definition and examples

Related CWE

CWE-272: Least Privilege Violation

  • Status: Incomplete
  • Weakness Abstractions: Base

The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.

More about CWE-272 definition and examples

Related CWE

CWE-273: Improper Check for Dropped Privileges

  • Status: Incomplete
  • Weakness Abstractions: Base

The software attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded.

More about CWE-273 definition and examples

Related CWE

CWE-274: Improper Handling of Insufficient Privileges

  • Status: Draft
  • Weakness Abstractions: Base

The software does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses.

More about CWE-274 definition and examples

Related CWE

CWE-275: Permission Issues

  • Status: Draft
  • Weakness Abstractions: Category

This category has been deprecated. It was originally intended as a “catch-all” for environment issues for technologies that did not have their own CWE, but it introduced unnecessary depth and complexity to the Development View (CWE-699).

More about CWE-275 definition and examples

CWE-276: Incorrect Default Permissions

  • Status: Draft
  • Weakness Abstractions: Base

During installation, installed file permissions are set to allow anyone to modify those files.

More about CWE-276 definition and examples

Related CWE

CWE-277: Insecure Inherited Permissions

  • Status: Draft
  • Weakness Abstractions: Variant

A product defines a set of insecure permissions that are inherited by objects that are created by the program.

More about CWE-277 definition and examples

Related CWE

CWE-278: Insecure Preserved Inherited Permissions

  • Status: Incomplete
  • Weakness Abstractions: Variant

A product inherits a set of insecure permissions for an object, e.g. when copying from an archive file, without user awareness or involvement.

More about CWE-278 definition and examples

Related CWE

CWE-279: Incorrect Execution-Assigned Permissions

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-279 definition and examples

Related CWE

CWE-280: Improper Handling of Insufficient Permissions or Privileges

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-280 definition and examples

Related CWE

CWE-281: Improper Preservation of Permissions

  • Status: Draft
  • Weakness Abstractions: Base

This is resultant from errors that prevent the permissions from being preserved.

More about CWE-281 definition and examples

Related CWE

CWE-282: Improper Ownership Management

  • Status: Draft
  • Weakness Abstractions: Class

The software assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.

More about CWE-282 definition and examples

Related CWE

CWE-283: Unverified Ownership

  • Status: Draft
  • Weakness Abstractions: Base

The software does not properly verify that a critical resource is owned by the proper entity.

More about CWE-283 definition and examples

Related CWE

CWE-284: Improper Access Control

  • Status: Incomplete
  • Weakness Abstractions: Pillar

The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

More about CWE-284 definition and examples

CWE-285: Improper Authorization

  • Status: Draft
  • Weakness Abstractions: Class

The software does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

More about CWE-285 definition and examples

Related CWE

CWE-286: Incorrect User Management

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not properly manage a user within its environment.

More about CWE-286 definition and examples

Related CWE

CWE-287: Improper Authentication

  • Status: Draft
  • Weakness Abstractions: Class

When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct.

More about CWE-287 definition and examples

Related CWE

CWE-288: Authentication Bypass Using an Alternate Path or Channel

  • Status: Incomplete
  • Weakness Abstractions: Base

A product requires authentication, but the product has an alternate path or channel that does not require authentication.

More about CWE-288 definition and examples

Related CWE

CWE-289: Authentication Bypass by Alternate Name

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-289 definition and examples

Related CWE

CWE-290: Authentication Bypass by Spoofing

  • Status: Incomplete
  • Weakness Abstractions: Base

This attack-focused weakness is caused by improperly implemented authentication schemes that are subject to spoofing attacks.

More about CWE-290 definition and examples

Related CWE

CWE-291: Reliance on IP Address for Authentication

  • Status: Incomplete
  • Weakness Abstractions: Variant

This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350.

More about CWE-291 definition and examples

Related CWE

CWE-293: Using Referer Field for Authentication

  • Status: Draft
  • Weakness Abstractions: Variant

The referer field in HTTP requests can be easily modified and, as such, is not a valid means of message integrity checking.

More about CWE-293 definition and examples

Related CWE

CWE-294: Authentication Bypass by Capture-replay

  • Status: Incomplete
  • Weakness Abstractions: Base

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).

More about CWE-294 definition and examples

Related CWE

CWE-295: Improper Certificate Validation

  • Status: Draft
  • Weakness Abstractions: Base

The software does not validate, or incorrectly validates, a certificate.

More about CWE-295 definition and examples

Related CWE

CWE-296: Improper Following of a Certificate’s Chain of Trust

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-296 definition and examples

Related CWE

CWE-297: Improper Validation of Certificate with Host Mismatch

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-297 definition and examples

Related CWE

CWE-298: Improper Validation of Certificate Expiration

  • Status: Draft
  • Weakness Abstractions: Variant

A certificate expiration is not validated or is incorrectly validated, so trust may be assigned to certificates that have been abandoned due to age.

More about CWE-298 definition and examples

Related CWE

CWE-299: Improper Check for Certificate Revocation

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-299 definition and examples

Related CWE

CWE-300: Channel Accessible by Non-Endpoint

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-300 definition and examples

Related CWE

CWE-301: Reflection Attack in an Authentication Protocol

  • Status: Draft
  • Weakness Abstractions: Variant

Simple authentication protocols are subject to reflection attacks if a malicious user can use the target machine to impersonate a trusted user.

More about CWE-301 definition and examples

Related CWE

CWE-302: Authentication Bypass by Assumed-Immutable Data

  • Status: Incomplete
  • Weakness Abstractions: Variant

The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.

More about CWE-302 definition and examples

Related CWE

CWE-303: Incorrect Implementation of Authentication Algorithm

  • Status: Draft
  • Weakness Abstractions: Base

The requirements for the software dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.

More about CWE-303 definition and examples

Related CWE

CWE-304: Missing Critical Step in Authentication

  • Status: Draft
  • Weakness Abstractions: Base

The software implements an authentication technique, but it skips a step that weakens the technique.

More about CWE-304 definition and examples

Related CWE

CWE-305: Authentication Bypass by Primary Weakness

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-305 definition and examples

Related CWE

CWE-306: Missing Authentication for Critical Function

  • Status: Draft
  • Weakness Abstractions: Base

The software does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

More about CWE-306 definition and examples

Related CWE

CWE-307: Improper Restriction of Excessive Authentication Attempts

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-307 definition and examples

Related CWE

CWE-308: Use of Single-factor Authentication

  • Status: Draft
  • Weakness Abstractions: Base

The use of single-factor authentication can lead to unnecessary risk of compromise when compared with the benefits of a dual-factor authentication scheme.

More about CWE-308 definition and examples

Related CWE

CWE-309: Use of Password System for Primary Authentication

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-309 definition and examples

Related CWE

CWE-310: Cryptographic Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and implementation of data confidentiality and integrity. Frequently these deal with the use of encoding techniques, encryption libraries, and hashing algorithms. The weaknesses in this category could lead to a degradation of the quality data if they are not addressed.

More about CWE-310 definition and examples

CWE-311: Missing Encryption of Sensitive Data

  • Status: Draft
  • Weakness Abstractions: Class

The software does not encrypt sensitive or critical information before storage or transmission.

More about CWE-311 definition and examples

Related CWE

CWE-312: Cleartext Storage of Sensitive Information

  • Status: Draft
  • Weakness Abstractions: Base

The application stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

More about CWE-312 definition and examples

Related CWE

CWE-313: Cleartext Storage in a File or on Disk

  • Status: Draft
  • Weakness Abstractions: Variant

The application stores sensitive information in cleartext in a file, or on disk.

More about CWE-313 definition and examples

Related CWE

CWE-314: Cleartext Storage in the Registry

  • Status: Draft
  • Weakness Abstractions: Variant

The application stores sensitive information in cleartext in the registry.

More about CWE-314 definition and examples

Related CWE

  • Status: Draft
  • Weakness Abstractions: Variant

The application stores sensitive information in cleartext in a cookie.

More about CWE-315 definition and examples

Related CWE

CWE-316: Cleartext Storage of Sensitive Information in Memory

  • Status: Draft
  • Weakness Abstractions: Variant

The application stores sensitive information in cleartext in memory.

More about CWE-316 definition and examples

Related CWE

CWE-317: Cleartext Storage of Sensitive Information in GUI

  • Status: Draft
  • Weakness Abstractions: Variant

The application stores sensitive information in cleartext within the GUI.

More about CWE-317 definition and examples

Related CWE

CWE-318: Cleartext Storage of Sensitive Information in Executable

  • Status: Draft
  • Weakness Abstractions: Variant

The application stores sensitive information in cleartext in an executable.

More about CWE-318 definition and examples

Related CWE

CWE-319: Cleartext Transmission of Sensitive Information

  • Status: Draft
  • Weakness Abstractions: Base

The software transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

More about CWE-319 definition and examples

Related CWE

CWE-320: Key Management Errors

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to errors in the management of cryptographic keys.

More about CWE-320 definition and examples

CWE-321: Use of Hard-coded Cryptographic Key

  • Status: Draft
  • Weakness Abstractions: Variant

The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.

More about CWE-321 definition and examples

Related CWE

CWE-322: Key Exchange without Entity Authentication

  • Status: Draft
  • Weakness Abstractions: Base

The software performs a key exchange with an actor without verifying the identity of that actor.

More about CWE-322 definition and examples

Related CWE

CWE-323: Reusing a Nonce, Key Pair in Encryption

  • Status: Incomplete
  • Weakness Abstractions: Variant

Nonces should be used for the present occasion and only once.

More about CWE-323 definition and examples

Related CWE

CWE-324: Use of a Key Past its Expiration Date

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-324 definition and examples

Related CWE

CWE-325: Missing Cryptographic Step

  • Status: Draft
  • Weakness Abstractions: Base

The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.

More about CWE-325 definition and examples

Related CWE

CWE-326: Inadequate Encryption Strength

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-326 definition and examples

Related CWE

CWE-327: Use of a Broken or Risky Cryptographic Algorithm

  • Status: Draft
  • Weakness Abstractions: Class

The use of a broken or risky cryptographic algorithm is an unnecessary risk that may result in the exposure of sensitive information.

More about CWE-327 definition and examples

Related CWE

CWE-328: Reversible One-Way Hash

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-328 definition and examples

Related CWE

CWE-329: Not Using an Unpredictable IV with CBC Mode

  • Status: Draft
  • Weakness Abstractions: Variant

Not using an unpredictable initialization Vector (IV) with Cipher Block Chaining (CBC) Mode causes algorithms to be susceptible to dictionary attacks when they are encrypted under the same key.

More about CWE-329 definition and examples

Related CWE

CWE-330: Use of Insufficiently Random Values

  • Status: Stable
  • Weakness Abstractions: Class

The software uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.

More about CWE-330 definition and examples

Related CWE

CWE-331: Insufficient Entropy

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-331 definition and examples

Related CWE

CWE-332: Insufficient Entropy in PRNG

  • Status: Draft
  • Weakness Abstractions: Variant

The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat.

More about CWE-332 definition and examples

Related CWE

CWE-333: Improper Handling of Insufficient Entropy in TRNG

  • Status: Draft
  • Weakness Abstractions: Variant

True random number generators (TRNG) generally have a limited source of entropy and therefore can fail or block.

More about CWE-333 definition and examples

Related CWE

CWE-334: Small Space of Random Values

  • Status: Draft
  • Weakness Abstractions: Base

The number of possible random values is smaller than needed by the product, making it more susceptible to brute force attacks.

More about CWE-334 definition and examples

Related CWE

CWE-335: Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)

  • Status: Draft
  • Weakness Abstractions: Base

The software uses a Pseudo-Random Number Generator (PRNG) that does not correctly manage seeds.

More about CWE-335 definition and examples

Related CWE

CWE-336: Same Seed in Pseudo-Random Number Generator (PRNG)

  • Status: Draft
  • Weakness Abstractions: Variant

A Pseudo-Random Number Generator (PRNG) uses the same seed each time the product is initialized.

More about CWE-336 definition and examples

Related CWE

CWE-337: Predictable Seed in Pseudo-Random Number Generator (PRNG)

  • Status: Draft
  • Weakness Abstractions: Variant

A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time.

More about CWE-337 definition and examples

Related CWE

CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

  • Status: Draft
  • Weakness Abstractions: Base

The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG’s algorithm is not cryptographically strong.

More about CWE-338 definition and examples

Related CWE

CWE-339: Small Seed Space in PRNG

  • Status: Draft
  • Weakness Abstractions: Variant

A PRNG uses a relatively small space of seeds.

More about CWE-339 definition and examples

Related CWE

CWE-340: Generation of Predictable Numbers or Identifiers

  • Status: Incomplete
  • Weakness Abstractions: Class

The product uses a scheme that generates numbers or identifiers that are more predictable than required.

More about CWE-340 definition and examples

Related CWE

CWE-341: Predictable from Observable State

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-341 definition and examples

Related CWE

CWE-342: Predictable Exact Value from Previous Values

  • Status: Draft
  • Weakness Abstractions: Base

An exact value or random number can be precisely predicted by observing previous values.

More about CWE-342 definition and examples

Related CWE

CWE-343: Predictable Value Range from Previous Values

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-343 definition and examples

Related CWE

CWE-344: Use of Invariant Value in Dynamically Changing Context

  • Status: Draft
  • Weakness Abstractions: Base

The product uses a constant value, name, or reference, but this value can (or should) vary across different environments.

More about CWE-344 definition and examples

Related CWE

CWE-345: Insufficient Verification of Data Authenticity

  • Status: Draft
  • Weakness Abstractions: Class

The software does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

More about CWE-345 definition and examples

Related CWE

CWE-346: Origin Validation Error

  • Status: Draft
  • Weakness Abstractions: Base

The software does not properly verify that the source of data or communication is valid.

More about CWE-346 definition and examples

Related CWE

CWE-347: Improper Verification of Cryptographic Signature

  • Status: Draft
  • Weakness Abstractions: Base

The software does not verify, or incorrectly verifies, the cryptographic signature for data.

More about CWE-347 definition and examples

Related CWE

CWE-348: Use of Less Trusted Source

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-348 definition and examples

Related CWE

CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-349 definition and examples

Related CWE

CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-350 definition and examples

Related CWE

CWE-351: Insufficient Type Distinction

  • Status: Draft
  • Weakness Abstractions: Base

The software does not properly distinguish between different types of elements in a way that leads to insecure behavior.

More about CWE-351 definition and examples

Related CWE

CWE-352: Cross-Site Request Forgery (CSRF)

  • Status: Stable
  • Weakness Abstractions: Compound

The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.

More about CWE-352 definition and examples

Related CWE

CWE-353: Missing Support for Integrity Check

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-353 definition and examples

Related CWE

CWE-354: Improper Validation of Integrity Check Value

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-354 definition and examples

Related CWE

CWE-355: User Interface Security Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to or introduced in the User Interface (UI).

More about CWE-355 definition and examples

CWE-356: Product UI does not Warn User of Unsafe Actions

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-356 definition and examples

Related CWE

CWE-357: Insufficient UI Warning of Dangerous Operations

  • Status: Draft
  • Weakness Abstractions: Base

The user interface provides a warning to a user regarding dangerous or sensitive operations, but the warning is not noticeable enough to warrant attention.

More about CWE-357 definition and examples

Related CWE

CWE-358: Improperly Implemented Security Check for Standard

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-358 definition and examples

Related CWE

CWE-359: Exposure of Private Personal Information to an Unauthorized Actor

  • Status: Incomplete
  • Weakness Abstractions: Base

The product does not properly prevent a person’s private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.

More about CWE-359 definition and examples

Related CWE

CWE-360: Trust of System Event Data

  • Status: Incomplete
  • Weakness Abstractions: Base

Security based on event locations are insecure and can be spoofed.

More about CWE-360 definition and examples

Related CWE

CWE-361: 7PK - Time and State

  • Status: Incomplete
  • Weakness Abstractions: Category

This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses related to the improper management of time and state in an environment that supports simultaneous or near-simultaneous computation by multiple systems, processes, or threads. According to the authors of the Seven Pernicious Kingdoms, “Distributed computation is about time and state. That is, in order for more than one component to communicate, state must be shared, and all that takes time. Most programmers anthropomorphize their work. They think about one thread of control carrying out the entire program in the same way they would if they had to do the job themselves. Modern computers, however, switch between tasks very quickly, and in multi-core, multi-CPU, or distributed systems, two events may take place at exactly the same time. Defects rush to fill the gap between the programmer’s model of how a program executes and what happens in reality. These defects are related to unexpected interactions between threads, processes, time, and information. These interactions happen through shared state: semaphores, variables, the file system, and, basically, anything that can store information.”

More about CWE-361 definition and examples

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization (‘Race Condition’)

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-362 definition and examples

Related CWE

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-363 definition and examples

Related CWE

CWE-364: Signal Handler Race Condition

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a signal handler that introduces a race condition.

More about CWE-364 definition and examples

Related CWE

CWE-365: Race Condition in Switch

  • Status: Draft
  • Weakness Abstractions: Base

The code contains a switch statement in which the switched variable can be modified while the switch is still executing, resulting in unexpected behavior.

More about CWE-365 definition and examples

Related CWE

CWE-366: Race Condition within a Thread

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-366 definition and examples

Related CWE

CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-367 definition and examples

Related CWE

CWE-368: Context Switching Race Condition

  • Status: Draft
  • Weakness Abstractions: Base

This weakness can be resultant from insufficient compartmentalization (CWE-653), incorrect locking, improper initialization or shutdown, or a number of other weaknesses.

More about CWE-368 definition and examples

Related CWE

CWE-369: Divide By Zero

  • Status: Draft
  • Weakness Abstractions: Base

The product divides a value by zero.

More about CWE-369 definition and examples

Related CWE

CWE-370: Missing Check for Certificate Revocation after Initial Check

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-370 definition and examples

Related CWE

CWE-371: State Issues

  • Status: Draft
  • Weakness Abstractions: Category

This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.

More about CWE-371 definition and examples

CWE-372: Incomplete Internal State Distinction

  • Status: Draft
  • Weakness Abstractions: Base

This entry was deprecated because it overlapped the same concepts as race condition (CWE-362) and Improper Synchronization (CWE-662).

More about CWE-372 definition and examples

Related CWE

CWE-374: Passing Mutable Objects to an Untrusted Method

  • Status: Draft
  • Weakness Abstractions: Base

The program sends non-cloned mutable data as an argument to a method or function.

More about CWE-374 definition and examples

Related CWE

CWE-375: Returning a Mutable Object to an Untrusted Caller

  • Status: Draft
  • Weakness Abstractions: Base

Sending non-cloned mutable data as a return value may result in that data being altered or deleted by the calling function.

More about CWE-375 definition and examples

Related CWE

CWE-377: Insecure Temporary File

  • Status: Incomplete
  • Weakness Abstractions: Class

Creating and using insecure temporary files can leave application and system data vulnerable to attack.

More about CWE-377 definition and examples

Related CWE

CWE-378: Creation of Temporary File With Insecure Permissions

  • Status: Draft
  • Weakness Abstractions: Base

Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.

More about CWE-378 definition and examples

Related CWE

CWE-379: Creation of Temporary File in Directory with Insecure Permissions

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-379 definition and examples

Related CWE

CWE-382: J2EE Bad Practices: Use of System.exit()

  • Status: Draft
  • Weakness Abstractions: Variant

A J2EE application uses System.exit(), which also shuts down its container.

More about CWE-382 definition and examples

Related CWE

CWE-383: J2EE Bad Practices: Direct Use of Threads

  • Status: Draft
  • Weakness Abstractions: Variant

Thread management in a Web application is forbidden in some circumstances and is always highly error prone.

More about CWE-383 definition and examples

Related CWE

CWE-384: Session Fixation

  • Status: Incomplete
  • Weakness Abstractions: Compound

Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.

More about CWE-384 definition and examples

Related CWE

CWE-385: Covert Timing Channel

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-385 definition and examples

Related CWE

CWE-386: Symbolic Name not Mapping to Correct Object

  • Status: Draft
  • Weakness Abstractions: Base

A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.

More about CWE-386 definition and examples

Related CWE

CWE-387: Signal Errors

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the improper handling of signals.

More about CWE-387 definition and examples

CWE-388: 7PK - Errors

  • Status: Draft
  • Weakness Abstractions: Category

This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that occur when an application does not properly handle errors that occur during processing. According to the authors of the Seven Pernicious Kingdoms, “Errors and error handling represent a class of API. Errors related to error handling are so common that they deserve a special kingdom of their own. As with ‘API Abuse,’ there are two ways to introduce an error-related security vulnerability: the most common one is handling errors poorly (or not at all). The second is producing errors that either give out too much information (to possible attackers) or are difficult to handle.”

More about CWE-388 definition and examples

CWE-389: Error Conditions, Return Values, Status Codes

  • Status: Incomplete
  • Weakness Abstractions: Category

This category includes weaknesses that occur if a function does not generate the correct return/status code, or if the application does not handle all possible return/status codes that could be generated by a function. This type of problem is most often found in conditions that are rarely encountered during the normal operation of the product. Presumably, most bugs related to common conditions are found and eliminated during development and testing. In some cases, the attacker can directly control or influence the environment to trigger the rare conditions.

More about CWE-389 definition and examples

CWE-390: Detection of Error Condition Without Action

  • Status: Draft
  • Weakness Abstractions: Base

The software detects a specific error, but takes no actions to handle the error.

More about CWE-390 definition and examples

Related CWE

CWE-391: Unchecked Error Condition

  • Status: Incomplete
  • Weakness Abstractions: Base

[PLANNED FOR DEPRECATION. SEE MAINTENANCE NOTES AND CONSIDER CWE-252, CWE-248, OR CWE-1069.] Ignoring exceptions and other error conditions may allow an attacker to induce unexpected behavior unnoticed.

More about CWE-391 definition and examples

Related CWE

CWE-392: Missing Report of Error Condition

  • Status: Draft
  • Weakness Abstractions: Base

The software encounters an error but does not provide a status code or return value to indicate that an error has occurred.

More about CWE-392 definition and examples

Related CWE

CWE-393: Return of Wrong Status Code

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-393 definition and examples

Related CWE

CWE-394: Unexpected Status Code or Return Value

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-394 definition and examples

Related CWE

CWE-395: Use of NullPointerException Catch to Detect NULL Pointer Dereference

  • Status: Draft
  • Weakness Abstractions: Base

Catching NullPointerException should not be used as an alternative to programmatic checks to prevent dereferencing a null pointer.

More about CWE-395 definition and examples

Related CWE

CWE-396: Declaration of Catch for Generic Exception

  • Status: Draft
  • Weakness Abstractions: Base

Catching overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.

More about CWE-396 definition and examples

Related CWE

CWE-397: Declaration of Throws for Generic Exception

  • Status: Draft
  • Weakness Abstractions: Base

Throwing overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.

More about CWE-397 definition and examples

Related CWE

CWE-398: 7PK - Code Quality

  • Status: Draft
  • Weakness Abstractions: Category

This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that do not directly introduce a weakness or vulnerability, but indicate that the product has not been carefully developed or maintained. According to the authors of the Seven Pernicious Kingdoms, “Poor code quality leads to unpredictable behavior. From a user’s perspective that often manifests itself as poor usability. For an adversary it provides an opportunity to stress the system in unexpected ways.”

More about CWE-398 definition and examples

CWE-399: Resource Management Errors

  • Status: Draft
  • Weakness Abstractions: Category

This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.

More about CWE-399 definition and examples

CWE-400: Uncontrolled Resource Consumption

  • Status: Draft
  • Weakness Abstractions: Class

The software does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.

More about CWE-400 definition and examples

Related CWE

CWE-401: Missing Release of Memory after Effective Lifetime

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.

More about CWE-401 definition and examples

Related CWE

CWE-402: Transmission of Private Resources into a New Sphere (‘Resource Leak’)

  • Status: Draft
  • Weakness Abstractions: Class

The software makes resources available to untrusted parties when those resources are only intended to be accessed by the software.

More about CWE-402 definition and examples

Related CWE

CWE-403: Exposure of File Descriptor to Unintended Control Sphere (‘File Descriptor Leak’)

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-403 definition and examples

Related CWE

CWE-404: Improper Resource Shutdown or Release

  • Status: Draft
  • Weakness Abstractions: Class

Improper release or shutdown of resources can be resultant from improper error handling or insufficient resource tracking.

More about CWE-404 definition and examples

Related CWE

CWE-405: Asymmetric Resource Consumption (Amplification)

  • Status: Incomplete
  • Weakness Abstractions: Class

Software that does not appropriately monitor or control resource consumption can lead to adverse system performance.

More about CWE-405 definition and examples

Related CWE

CWE-406: Insufficient Control of Network Message Volume (Network Amplification)

  • Status: Incomplete
  • Weakness Abstractions: Class

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.

More about CWE-406 definition and examples

Related CWE

CWE-407: Inefficient Algorithmic Complexity

  • Status: Incomplete
  • Weakness Abstractions: Class

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.

More about CWE-407 definition and examples

Related CWE

CWE-408: Incorrect Behavior Order: Early Amplification

  • Status: Draft
  • Weakness Abstractions: Base

The software allows an entity to perform a legitimate but expensive operation before authentication or authorization has taken place.

More about CWE-408 definition and examples

Related CWE

CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)

  • Status: Incomplete
  • Weakness Abstractions: Base

The software does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

More about CWE-409 definition and examples

Related CWE

CWE-410: Insufficient Resource Pool

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-410 definition and examples

Related CWE

CWE-411: Resource Locking Problems

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to improper handling of locks that are used to control access to resources.

More about CWE-411 definition and examples

CWE-412: Unrestricted Externally Accessible Lock

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-412 definition and examples

Related CWE

CWE-413: Improper Resource Locking

  • Status: Draft
  • Weakness Abstractions: Base

The software does not lock or does not correctly lock a resource when the software must have exclusive access to the resource.

More about CWE-413 definition and examples

Related CWE

CWE-414: Missing Lock Check

  • Status: Draft
  • Weakness Abstractions: Base

A product does not check to see if a lock is present before performing sensitive operations on a resource.

More about CWE-414 definition and examples

Related CWE

CWE-415: Double Free

  • Status: Draft
  • Weakness Abstractions: Variant

The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.

More about CWE-415 definition and examples

Related CWE

CWE-416: Use After Free

  • Status: Stable
  • Weakness Abstractions: Variant

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

More about CWE-416 definition and examples

Related CWE

CWE-417: Communication Channel Errors

  • Status: Draft
  • Weakness Abstractions: Category

This category has been deprecated because it redundant with the grouping provided by CWE-417.

More about CWE-417 definition and examples

CWE-419: Unprotected Primary Channel

  • Status: Draft
  • Weakness Abstractions: Base

The software uses a primary channel for administration or restricted functionality, but it does not properly protect the channel.

More about CWE-419 definition and examples

Related CWE

CWE-420: Unprotected Alternate Channel

  • Status: Draft
  • Weakness Abstractions: Base

The software protects a primary channel, but it does not use the same level of protection for an alternate channel.

More about CWE-420 definition and examples

Related CWE

CWE-421: Race Condition During Access to Alternate Channel

  • Status: Draft
  • Weakness Abstractions: Base

The product opens an alternate channel to communicate with an authorized user, but the channel is accessible to other actors.

More about CWE-421 definition and examples

Related CWE

CWE-422: Unprotected Windows Messaging Channel (‘Shatter’)

  • Status: Draft
  • Weakness Abstractions: Variant

This entry has been deprecated because it was a duplicate of CWE-441. All content has been transferred to CWE-441.

More about CWE-422 definition and examples

Related CWE

CWE-424: Improper Protection of Alternate Path

  • Status: Draft
  • Weakness Abstractions: Class

The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources.

More about CWE-424 definition and examples

Related CWE

CWE-425: Direct Request (‘Forced Browsing’)

  • Status: Incomplete
  • Weakness Abstractions: Base

The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.

More about CWE-425 definition and examples

Related CWE

CWE-426: Untrusted Search Path

  • Status: Stable
  • Weakness Abstractions: Base

The application searches for critical resources using an externally-supplied search path that can point to resources that are not under the application’s direct control.

More about CWE-426 definition and examples

Related CWE

CWE-427: Uncontrolled Search Path Element

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-427 definition and examples

Related CWE

CWE-428: Unquoted Search Path or Element

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-428 definition and examples

Related CWE

CWE-429: Handler Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to improper management of handlers.

More about CWE-429 definition and examples

CWE-430: Deployment of Wrong Handler

  • Status: Incomplete
  • Weakness Abstractions: Base

This weakness is usually resultant from other weaknesses.

More about CWE-430 definition and examples

Related CWE

CWE-431: Missing Handler

  • Status: Draft
  • Weakness Abstractions: Base

A handler is not available or implemented.

More about CWE-431 definition and examples

Related CWE

CWE-432: Dangerous Signal Handler not Disabled During Sensitive Operations

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-432 definition and examples

Related CWE

CWE-433: Unparsed Raw Web Content Delivery

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.

More about CWE-433 definition and examples

Related CWE

CWE-434: Unrestricted Upload of File with Dangerous Type

  • Status: Draft
  • Weakness Abstractions: Base

This can be resultant from client-side enforcement (CWE-602); some products will include web script in web clients to check the filename, without verifying on the server side.

More about CWE-434 definition and examples

Related CWE

CWE-435: Improper Interaction Between Multiple Correctly-Behaving Entities

  • Status: Draft
  • Weakness Abstractions: Pillar

An interaction error occurs when two entities have correct behavior when running independently of each other, but when they are integrated as components in a larger system or process, they introduce incorrect behaviors that may cause resultant weaknesses.

More about CWE-435 definition and examples

CWE-436: Interpretation Conflict

  • Status: Incomplete
  • Weakness Abstractions: Class

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.

More about CWE-436 definition and examples

Related CWE

CWE-437: Incomplete Model of Endpoint Features

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-437 definition and examples

Related CWE

CWE-438: Behavioral Problems

  • Status: Draft
  • Weakness Abstractions: Category

This weakness has been deprecated because it was a duplicate of CWE-355. All content has been transferred to CWE-355.

More about CWE-438 definition and examples

CWE-439: Behavioral Change in New Version or Environment

  • Status: Draft
  • Weakness Abstractions: Base

A’s behavior or functionality changes with a new version of A, or a new environment, which is not known (or manageable) by B.

More about CWE-439 definition and examples

Related CWE

CWE-440: Expected Behavior Violation

  • Status: Draft
  • Weakness Abstractions: Base

A feature, API, or function does not perform according to its specification.

More about CWE-440 definition and examples

Related CWE

CWE-441: Unintended Proxy or Intermediary (‘Confused Deputy’)

  • Status: Draft
  • Weakness Abstractions: Class

This weakness can be found at CWE-113.

More about CWE-441 definition and examples

Related CWE

CWE-444: Inconsistent Interpretation of HTTP Requests (‘HTTP Request Smuggling’)

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-444 definition and examples

Related CWE

CWE-446: UI Discrepancy for Security Feature

  • Status: Incomplete
  • Weakness Abstractions: Class

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.

More about CWE-446 definition and examples

Related CWE

CWE-447: Unimplemented or Unsupported Feature in UI

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-447 definition and examples

Related CWE

CWE-448: Obsolete Feature in UI

  • Status: Draft
  • Weakness Abstractions: Base

A UI function is obsolete and the product does not warn the user.

More about CWE-448 definition and examples

Related CWE

CWE-449: The UI Performs the Wrong Action

  • Status: Incomplete
  • Weakness Abstractions: Base

The UI performs the wrong action with respect to the user’s request.

More about CWE-449 definition and examples

Related CWE

CWE-450: Multiple Interpretations of UI Input

  • Status: Draft
  • Weakness Abstractions: Base

The UI has multiple interpretations of user input but does not prompt the user when it selects the less secure interpretation.

More about CWE-450 definition and examples

Related CWE

CWE-451: User Interface (UI) Misrepresentation of Critical Information

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-451 definition and examples

Related CWE

CWE-452: Initialization and Cleanup Errors

  • Status: Draft
  • Weakness Abstractions: Category

This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.

More about CWE-452 definition and examples

CWE-453: Insecure Default Variable Initialization

  • Status: Draft
  • Weakness Abstractions: Variant

The software, by default, initializes an internal variable with an insecure or less secure value than is possible.

More about CWE-453 definition and examples

Related CWE

CWE-454: External Initialization of Trusted Variables or Data Stores

  • Status: Draft
  • Weakness Abstractions: Base

The software initializes critical internal variables or data stores using inputs that can be modified by untrusted actors.

More about CWE-454 definition and examples

Related CWE

CWE-455: Non-exit on Failed Initialization

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-455 definition and examples

Related CWE

CWE-456: Missing Initialization of a Variable

  • Status: Draft
  • Weakness Abstractions: Variant

The software does not initialize critical variables, which causes the execution environment to use unexpected values.

More about CWE-456 definition and examples

Related CWE

CWE-457: Use of Uninitialized Variable

  • Status: Draft
  • Weakness Abstractions: Variant

This weakness has been deprecated because its name and description did not match. The description duplicated CWE-454, while the name suggested a more abstract initialization problem. Please refer to CWE-665 for the more abstract problem.

More about CWE-457 definition and examples

Related CWE

CWE-459: Incomplete Cleanup

  • Status: Draft
  • Weakness Abstractions: Base

The software does not properly “clean up” and remove temporary or supporting resources after they have been used.

More about CWE-459 definition and examples

Related CWE

CWE-460: Improper Cleanup on Thrown Exception

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-460 definition and examples

Related CWE

CWE-462: Duplicate Key in Associative List (Alist)

  • Status: Incomplete
  • Weakness Abstractions: Base

Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error.

More about CWE-462 definition and examples

Related CWE

CWE-463: Deletion of Data Structure Sentinel

  • Status: Incomplete
  • Weakness Abstractions: Base

The accidental deletion of a data-structure sentinel can cause serious programming logic problems.

More about CWE-463 definition and examples

Related CWE

CWE-464: Addition of Data Structure Sentinel

  • Status: Incomplete
  • Weakness Abstractions: Base

The accidental addition of a data-structure sentinel can cause serious programming logic problems.

More about CWE-464 definition and examples

Related CWE

CWE-465: Pointer Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to improper handling of pointers.

More about CWE-465 definition and examples

CWE-466: Return of Pointer Value Outside of Expected Range

  • Status: Draft
  • Weakness Abstractions: Base

A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference.

More about CWE-466 definition and examples

Related CWE

CWE-467: Use of sizeof() on a Pointer Type

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-467 definition and examples

Related CWE

CWE-468: Incorrect Pointer Scaling

  • Status: Incomplete
  • Weakness Abstractions: Base

In C and C++, one may often accidentally refer to the wrong memory due to the semantics of when math operations are implicitly scaled.

More about CWE-468 definition and examples

Related CWE

CWE-469: Use of Pointer Subtraction to Determine Size

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-469 definition and examples

Related CWE

CWE-470: Use of Externally-Controlled Input to Select Classes or Code (‘Unsafe Reflection’)

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-470 definition and examples

Related CWE

CWE-471: Modification of Assumed-Immutable Data (MAID)

  • Status: Draft
  • Weakness Abstractions: Base

The software does not properly protect an assumed-immutable element from being modified by an attacker.

More about CWE-471 definition and examples

Related CWE

CWE-472: External Control of Assumed-Immutable Web Parameter

  • Status: Draft
  • Weakness Abstractions: Base

The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields.

More about CWE-472 definition and examples

Related CWE

CWE-473: PHP External Variable Modification

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-473 definition and examples

Related CWE

CWE-474: Use of Function with Inconsistent Implementations

  • Status: Draft
  • Weakness Abstractions: Base

The code uses a function that has inconsistent implementations across operating systems and versions.

More about CWE-474 definition and examples

Related CWE

CWE-475: Undefined Behavior for Input to API

  • Status: Incomplete
  • Weakness Abstractions: Base

The behavior of this function is undefined unless its control parameter is set to a specific value.

More about CWE-475 definition and examples

Related CWE

CWE-476: NULL Pointer Dereference

  • Status: Stable
  • Weakness Abstractions: Base

NULL pointer dereferences are frequently resultant from rarely encountered error conditions, since these are most likely to escape detection during the testing phases.

More about CWE-476 definition and examples

Related CWE

CWE-477: Use of Obsolete Function

  • Status: Draft
  • Weakness Abstractions: Base

The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.

More about CWE-477 definition and examples

Related CWE

CWE-478: Missing Default Case in Switch Statement

  • Status: Draft
  • Weakness Abstractions: Base

The code does not have a default case in a switch statement, which might lead to complex logical errors and resultant weaknesses.

More about CWE-478 definition and examples

Related CWE

CWE-479: Signal Handler Use of a Non-reentrant Function

  • Status: Draft
  • Weakness Abstractions: Variant

The program defines a signal handler that calls a non-reentrant function.

More about CWE-479 definition and examples

Related CWE

CWE-480: Use of Incorrect Operator

  • Status: Draft
  • Weakness Abstractions: Base

The programmer accidentally uses the wrong operator, which changes the application logic in security-relevant ways.

More about CWE-480 definition and examples

Related CWE

CWE-481: Assigning instead of Comparing

  • Status: Draft
  • Weakness Abstractions: Variant

The code uses an operator for assignment when the intention was to perform a comparison.

More about CWE-481 definition and examples

Related CWE

CWE-482: Comparing instead of Assigning

  • Status: Draft
  • Weakness Abstractions: Variant

The code uses an operator for comparison when the intention was to perform an assignment.

More about CWE-482 definition and examples

Related CWE

CWE-483: Incorrect Block Delimitation

  • Status: Draft
  • Weakness Abstractions: Base

The code does not explicitly delimit a block that is intended to contain 2 or more statements, creating a logic error.

More about CWE-483 definition and examples

Related CWE

CWE-484: Omitted Break Statement in Switch

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-484 definition and examples

Related CWE

CWE-485: 7PK - Encapsulation

  • Status: Draft
  • Weakness Abstractions: Category

This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.

More about CWE-485 definition and examples

CWE-486: Comparison of Classes by Name

  • Status: Draft
  • Weakness Abstractions: Variant

The program compares classes by name, which can cause it to use the wrong class when multiple classes can have the same name.

More about CWE-486 definition and examples

Related CWE

CWE-487: Reliance on Package-level Scope

  • Status: Incomplete
  • Weakness Abstractions: Base

Java packages are not inherently closed; therefore, relying on them for code security is not a good practice.

More about CWE-487 definition and examples

Related CWE

CWE-488: Exposure of Data Element to Wrong Session

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-488 definition and examples

Related CWE

CWE-489: Active Debug Code

  • Status: Draft
  • Weakness Abstractions: Base

The application is deployed to unauthorized actors with debugging code still enabled or active, which can create unintended entry points or expose sensitive information.

More about CWE-489 definition and examples

Related CWE

CWE-491: Public cloneable() Method Without Final (‘Object Hijack’)

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-491 definition and examples

Related CWE

CWE-492: Use of Inner Class Containing Sensitive Data

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-492 definition and examples

Related CWE

CWE-493: Critical Public Variable Without Final Modifier

  • Status: Draft
  • Weakness Abstractions: Variant

The product has a critical public variable that is not final, which allows the variable to be modified to contain unexpected values.

More about CWE-493 definition and examples

Related CWE

CWE-494: Download of Code Without Integrity Check

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-494 definition and examples

Related CWE

CWE-495: Private Data Structure Returned From A Public Method

  • Status: Draft
  • Weakness Abstractions: Variant

The product has a method that is declared public, but returns a reference to a private data structure, which could then be modified in unexpected ways.

More about CWE-495 definition and examples

Related CWE

CWE-496: Public Data Assigned to Private Array-Typed Field

  • Status: Incomplete
  • Weakness Abstractions: Variant

Assigning public data to a private array is equivalent to giving public access to the array.

More about CWE-496 definition and examples

Related CWE

CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere

  • Status: Incomplete
  • Weakness Abstractions: Base

The application does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the application does.

More about CWE-497 definition and examples

Related CWE

CWE-498: Cloneable Class Containing Sensitive Information

  • Status: Draft
  • Weakness Abstractions: Variant

The code contains a class with sensitive data, but the class is cloneable. The data can then be accessed by cloning the class.

More about CWE-498 definition and examples

Related CWE

CWE-499: Serializable Class Containing Sensitive Data

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-499 definition and examples

Related CWE

CWE-500: Public Static Field Not Marked Final

  • Status: Draft
  • Weakness Abstractions: Variant

An object contains a public static field that is not marked final, which might allow it to be modified in unexpected ways.

More about CWE-500 definition and examples

Related CWE

CWE-501: Trust Boundary Violation

  • Status: Draft
  • Weakness Abstractions: Base

The product mixes trusted and untrusted data in the same data structure or structured message.

More about CWE-501 definition and examples

Related CWE

CWE-502: Deserialization of Untrusted Data

  • Status: Draft
  • Weakness Abstractions: Base

The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.

More about CWE-502 definition and examples

Related CWE

CWE-506: Embedded Malicious Code

  • Status: Incomplete
  • Weakness Abstractions: Class

The application contains code that appears to be malicious in nature.

More about CWE-506 definition and examples

Related CWE

CWE-507: Trojan Horse

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-507 definition and examples

Related CWE

CWE-508: Non-Replicating Malicious Code

  • Status: Incomplete
  • Weakness Abstractions: Base

Non-replicating malicious code only resides on the target system or software that is attacked; it does not attempt to spread to other systems.

More about CWE-508 definition and examples

Related CWE

CWE-509: Replicating Malicious Code (Virus or Worm)

  • Status: Incomplete
  • Weakness Abstractions: Base

Replicating malicious code, including viruses and worms, will attempt to attack other systems once it has successfully compromised the target system or software.

More about CWE-509 definition and examples

Related CWE

CWE-510: Trapdoor

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-510 definition and examples

Related CWE

CWE-511: Logic/Time Bomb

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-511 definition and examples

Related CWE

CWE-512: Spyware

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-512 definition and examples

Related CWE

CWE-514: Covert Channel

  • Status: Incomplete
  • Weakness Abstractions: Class

A covert channel is a path that can be used to transfer information in a way not intended by the system’s designers.

More about CWE-514 definition and examples

Related CWE

CWE-515: Covert Storage Channel

  • Status: Incomplete
  • Weakness Abstractions: Base

This weakness can be found at CWE-385.

More about CWE-515 definition and examples

Related CWE

CWE-520: .NET Misconfiguration: Use of Impersonation

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-520 definition and examples

Related CWE

CWE-521: Weak Password Requirements

  • Status: Draft
  • Weakness Abstractions: Base

The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts.

More about CWE-521 definition and examples

Related CWE

CWE-522: Insufficiently Protected Credentials

  • Status: Incomplete
  • Weakness Abstractions: Class

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

More about CWE-522 definition and examples

Related CWE

CWE-523: Unprotected Transport of Credentials

  • Status: Incomplete
  • Weakness Abstractions: Base

Login pages do not use adequate measures to protect the user name and password while they are in transit from the client to the server.

More about CWE-523 definition and examples

Related CWE

CWE-524: Use of Cache Containing Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Base

The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.

More about CWE-524 definition and examples

Related CWE

CWE-525: Use of Web Browser Cache Containing Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Variant

The web application does not use an appropriate caching policy that specifies the extent to which each web page and associated form fields should be cached.

More about CWE-525 definition and examples

Related CWE

CWE-526: Exposure of Sensitive Information Through Environmental Variables

  • Status: Incomplete
  • Weakness Abstractions: Variant

Environmental variables may contain sensitive information about a remote server.

More about CWE-526 definition and examples

Related CWE

CWE-527: Exposure of Version-Control Repository to an Unauthorized Control Sphere

  • Status: Incomplete
  • Weakness Abstractions: Variant

The product stores a CVS, git, or other repository in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.

More about CWE-527 definition and examples

Related CWE

CWE-528: Exposure of Core Dump File to an Unauthorized Control Sphere

  • Status: Draft
  • Weakness Abstractions: Variant

The product generates a core dump file in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.

More about CWE-528 definition and examples

Related CWE

CWE-529: Exposure of Access Control List Files to an Unauthorized Control Sphere

  • Status: Incomplete
  • Weakness Abstractions: Variant

The product stores access control list files in a directory or other container that is accessible to actors outside of the intended control sphere.

More about CWE-529 definition and examples

Related CWE

CWE-530: Exposure of Backup File to an Unauthorized Control Sphere

  • Status: Incomplete
  • Weakness Abstractions: Variant

A backup file is stored in a directory or archive that is made accessible to unauthorized actors.

More about CWE-530 definition and examples

Related CWE

CWE-531: Inclusion of Sensitive Information in Test Code

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-531 definition and examples

Related CWE

CWE-532: Insertion of Sensitive Information into Log File

  • Status: Incomplete
  • Weakness Abstractions: Base

This entry has been deprecated because its abstraction was too low-level. See CWE-532.

More about CWE-532 definition and examples

Related CWE

CWE-535: Exposure of Information Through Shell Error Message

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-535 definition and examples

Related CWE

CWE-536: Servlet Runtime Error Message Containing Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Variant

A servlet error message indicates that there exists an unhandled exception in your web application code and may provide useful information to an attacker.

More about CWE-536 definition and examples

Related CWE

CWE-537: Java Runtime Error Message Containing Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Variant

In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system.

More about CWE-537 definition and examples

Related CWE

CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory

  • Status: Draft
  • Weakness Abstractions: Base

The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.

More about CWE-538 definition and examples

Related CWE

CWE-539: Use of Persistent Cookies Containing Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Variant

The web application uses persistent cookies, but the cookies contain sensitive information.

More about CWE-539 definition and examples

Related CWE

CWE-540: Inclusion of Sensitive Information in Source Code

  • Status: Incomplete
  • Weakness Abstractions: Base

Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.

More about CWE-540 definition and examples

Related CWE

CWE-541: Inclusion of Sensitive Information in an Include File

  • Status: Incomplete
  • Weakness Abstractions: Variant

This entry has been deprecated because its abstraction was too low-level. See CWE-532.

More about CWE-541 definition and examples

Related CWE

CWE-543: Use of Singleton Pattern Without Synchronization in a Multithreaded Context

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software uses the singleton pattern when creating a resource within a multithreaded environment.

More about CWE-543 definition and examples

Related CWE

CWE-544: Missing Standardized Error Handling Mechanism

  • Status: Draft
  • Weakness Abstractions: Base

This weakness has been deprecated because it partially overlaps CWE-470, it describes legitimate programmer behavior, and other portions will need to be integrated into other entries.

More about CWE-544 definition and examples

Related CWE

CWE-546: Suspicious Comment

  • Status: Draft
  • Weakness Abstractions: Variant

The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses.

More about CWE-546 definition and examples

Related CWE

CWE-547: Use of Hard-coded, Security-relevant Constants

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-547 definition and examples

Related CWE

CWE-548: Exposure of Information Through Directory Listing

  • Status: Draft
  • Weakness Abstractions: Variant

A directory listing is inappropriately exposed, yielding potentially sensitive information to attackers.

More about CWE-548 definition and examples

Related CWE

CWE-549: Missing Password Field Masking

  • Status: Draft
  • Weakness Abstractions: Base

The software does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.

More about CWE-549 definition and examples

Related CWE

CWE-550: Server-generated Error Message Containing Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Variant

Certain conditions, such as network failure, will cause a server error message to be displayed.

More about CWE-550 definition and examples

Related CWE

CWE-551: Incorrect Behavior Order: Authorization Before Parsing and Canonicalization

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-551 definition and examples

Related CWE

CWE-552: Files or Directories Accessible to External Parties

  • Status: Draft
  • Weakness Abstractions: Base

The product makes files or directories accessible to unauthorized actors, even though they should not be.

More about CWE-552 definition and examples

Related CWE

CWE-553: Command Shell in Externally Accessible Directory

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-553 definition and examples

Related CWE

CWE-554: ASP.NET Misconfiguration: Not Using Input Validation Framework

  • Status: Draft
  • Weakness Abstractions: Variant

The ASP.NET application does not use an input validation framework.

More about CWE-554 definition and examples

Related CWE

CWE-555: J2EE Misconfiguration: Plaintext Password in Configuration File

  • Status: Draft
  • Weakness Abstractions: Variant

The J2EE application stores a plaintext password in a configuration file.

More about CWE-555 definition and examples

Related CWE

CWE-556: ASP.NET Misconfiguration: Use of Identity Impersonation

  • Status: Incomplete
  • Weakness Abstractions: Variant

Configuring an ASP.NET application to run with impersonated credentials may give the application unnecessary privileges.

More about CWE-556 definition and examples

Related CWE

CWE-557: Concurrency Issues

  • Status: Draft
  • Weakness Abstractions: Category

This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.

More about CWE-557 definition and examples

CWE-558: Use of getlogin() in Multithreaded Application

  • Status: Draft
  • Weakness Abstractions: Variant

The application uses the getlogin() function in a multithreaded context, potentially causing it to return incorrect values.

More about CWE-558 definition and examples

Related CWE

CWE-560: Use of umask() with chmod-style Argument

  • Status: Draft
  • Weakness Abstractions: Variant

The product calls umask() with an incorrect argument that is specified as if it is an argument to chmod().

More about CWE-560 definition and examples

Related CWE

CWE-561: Dead Code

  • Status: Draft
  • Weakness Abstractions: Base

The software contains dead code, which can never be executed.

More about CWE-561 definition and examples

Related CWE

CWE-562: Return of Stack Variable Address

  • Status: Draft
  • Weakness Abstractions: Base

A function returns the address of a stack variable, which will cause unintended program behavior, typically in the form of a crash.

More about CWE-562 definition and examples

Related CWE

CWE-563: Assignment to Variable without Use

  • Status: Draft
  • Weakness Abstractions: Variant

The variable’s value is assigned but never used, making it a dead store.

More about CWE-563 definition and examples

Related CWE

CWE-564: SQL Injection: Hibernate

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-564 definition and examples

Related CWE

CWE-565: Reliance on Cookies without Validation and Integrity Checking

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-565 definition and examples

Related CWE

CWE-566: Authorization Bypass Through User-Controlled SQL Primary Key

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-566 definition and examples

Related CWE

CWE-567: Unsynchronized Access to Shared Data in a Multithreaded Context

  • Status: Draft
  • Weakness Abstractions: Base

The product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes.

More about CWE-567 definition and examples

Related CWE

CWE-568: finalize() Method Without super.finalize()

  • Status: Draft
  • Weakness Abstractions: Variant

The software contains a finalize() method that does not call super.finalize().

More about CWE-568 definition and examples

Related CWE

CWE-569: Expression Issues

  • Status: Draft
  • Weakness Abstractions: Category

This category has been deprecated as it was found to be an unnecessary abstraction of platform specific details. Please refer to the category CWE-632 and weakness CWE-66 for relevant relationships.

More about CWE-569 definition and examples

CWE-570: Expression is Always False

  • Status: Draft
  • Weakness Abstractions: Base

The software contains an expression that will always evaluate to false.

More about CWE-570 definition and examples

Related CWE

CWE-571: Expression is Always True

  • Status: Draft
  • Weakness Abstractions: Base

The software contains an expression that will always evaluate to true.

More about CWE-571 definition and examples

Related CWE

CWE-572: Call to Thread run() instead of start()

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-572 definition and examples

Related CWE

CWE-573: Improper Following of Specification by Caller

  • Status: Draft
  • Weakness Abstractions: Class

The software does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform.

More about CWE-573 definition and examples

Related CWE

CWE-574: EJB Bad Practices: Use of Synchronization Primitives

  • Status: Draft
  • Weakness Abstractions: Variant

The program violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.

More about CWE-574 definition and examples

Related CWE

CWE-575: EJB Bad Practices: Use of AWT Swing

  • Status: Draft
  • Weakness Abstractions: Variant

The program violates the Enterprise JavaBeans (EJB) specification by using AWT/Swing.

More about CWE-575 definition and examples

Related CWE

CWE-576: EJB Bad Practices: Use of Java I/O

  • Status: Draft
  • Weakness Abstractions: Variant

The program violates the Enterprise JavaBeans (EJB) specification by using the java.io package.

More about CWE-576 definition and examples

Related CWE

CWE-577: EJB Bad Practices: Use of Sockets

  • Status: Draft
  • Weakness Abstractions: Variant

The program violates the Enterprise JavaBeans (EJB) specification by using sockets.

More about CWE-577 definition and examples

Related CWE

CWE-578: EJB Bad Practices: Use of Class Loader

  • Status: Draft
  • Weakness Abstractions: Variant

The program violates the Enterprise JavaBeans (EJB) specification by using the class loader.

More about CWE-578 definition and examples

Related CWE

CWE-579: J2EE Bad Practices: Non-serializable Object Stored in Session

  • Status: Draft
  • Weakness Abstractions: Variant

The application stores a non-serializable object as an HttpSession attribute, which can hurt reliability.

More about CWE-579 definition and examples

Related CWE

CWE-580: clone() Method Without super.clone()

  • Status: Draft
  • Weakness Abstractions: Variant

The software contains a clone() method that does not call super.clone() to obtain the new object.

More about CWE-580 definition and examples

Related CWE

CWE-581: Object Model Violation: Just One of Equals and Hashcode Defined

  • Status: Draft
  • Weakness Abstractions: Base

The software does not maintain equal hashcodes for equal objects.

More about CWE-581 definition and examples

Related CWE

CWE-582: Array Declared Public, Final, and Static

  • Status: Draft
  • Weakness Abstractions: Variant

The program declares an array public, final, and static, which is not sufficient to prevent the array’s contents from being modified.

More about CWE-582 definition and examples

Related CWE

CWE-583: finalize() Method Declared Public

  • Status: Incomplete
  • Weakness Abstractions: Variant

The program violates secure coding principles for mobile code by declaring a finalize() method public.

More about CWE-583 definition and examples

Related CWE

CWE-584: Return Inside Finally Block

  • Status: Draft
  • Weakness Abstractions: Base

The code has a return statement inside a finally block, which will cause any thrown exception in the try block to be discarded.

More about CWE-584 definition and examples

Related CWE

CWE-585: Empty Synchronized Block

  • Status: Draft
  • Weakness Abstractions: Base

The software contains an empty synchronized block.

More about CWE-585 definition and examples

Related CWE

CWE-586: Explicit Call to Finalize()

  • Status: Draft
  • Weakness Abstractions: Variant

The software makes an explicit call to the finalize() method from outside the finalizer.

More about CWE-586 definition and examples

Related CWE

CWE-587: Assignment of a Fixed Address to a Pointer

  • Status: Draft
  • Weakness Abstractions: Base

The software sets a pointer to a specific address other than NULL or 0.

More about CWE-587 definition and examples

Related CWE

CWE-588: Attempt to Access Child of a Non-structure Pointer

  • Status: Incomplete
  • Weakness Abstractions: Variant

Casting a non-structure type to a structure type and accessing a field can lead to memory access errors or data corruption.

More about CWE-588 definition and examples

Related CWE

CWE-589: Call to Non-ubiquitous API

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-589 definition and examples

Related CWE

CWE-590: Free of Memory not on the Heap

  • Status: Incomplete
  • Weakness Abstractions: Variant

The application calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().

More about CWE-590 definition and examples

Related CWE

CWE-591: Sensitive Data Storage in Improperly Locked Memory

  • Status: Draft
  • Weakness Abstractions: Variant

This weakness has been deprecated because it covered redundant concepts already described in CWE-287.

More about CWE-591 definition and examples

Related CWE

CWE-593: Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created

  • Status: Draft
  • Weakness Abstractions: Variant

The software modifies the SSL context after connection creation has begun.

More about CWE-593 definition and examples

Related CWE

CWE-594: J2EE Framework: Saving Unserializable Objects to Disk

  • Status: Incomplete
  • Weakness Abstractions: Variant

When the J2EE container attempts to write unserializable objects to disk there is no guarantee that the process will complete successfully.

More about CWE-594 definition and examples

Related CWE

CWE-595: Comparison of Object References Instead of Object Contents

  • Status: Incomplete
  • Weakness Abstractions: Variant

This weakness has been deprecated. It was poorly described and difficult to distinguish from other entries. It was also inappropriate to assign a separate ID solely because of domain-specific considerations. Its closest equivalent is CWE-1023.

More about CWE-595 definition and examples

Related CWE

CWE-597: Use of Wrong Operator in String Comparison

  • Status: Draft
  • Weakness Abstractions: Variant

The product uses the wrong operator when comparing a string, such as using “==” when the .equals() method should be used instead.

More about CWE-597 definition and examples

Related CWE

CWE-598: Use of GET Request Method With Sensitive Query Strings

  • Status: Draft
  • Weakness Abstractions: Variant

The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that requests.

More about CWE-598 definition and examples

Related CWE

CWE-599: Missing Validation of OpenSSL Certificate

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-599 definition and examples

Related CWE

CWE-600: Uncaught Exception in Servlet

  • Status: Draft
  • Weakness Abstractions: Base

The Servlet does not catch all exceptions, which may reveal sensitive debugging information.

More about CWE-600 definition and examples

Related CWE

CWE-601: URL Redirection to Untrusted Site (‘Open Redirect’)

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-601 definition and examples

Related CWE

CWE-602: Client-Side Enforcement of Server-Side Security

  • Status: Draft
  • Weakness Abstractions: Base

The software is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.

More about CWE-602 definition and examples

Related CWE

CWE-603: Use of Client-Side Authentication

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-603 definition and examples

Related CWE

CWE-605: Multiple Binds to the Same Port

  • Status: Draft
  • Weakness Abstractions: Base

When multiple sockets are allowed to bind to the same port, other services on that port may be stolen or spoofed.

More about CWE-605 definition and examples

Related CWE

CWE-606: Unchecked Input for Loop Condition

  • Status: Draft
  • Weakness Abstractions: Base

The product does not properly check inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.

More about CWE-606 definition and examples

Related CWE

CWE-607: Public Static Final Field References Mutable Object

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-607 definition and examples

Related CWE

CWE-608: Struts: Non-private Field in ActionForm Class

  • Status: Draft
  • Weakness Abstractions: Variant

An ActionForm class contains a field that has not been declared private, which can be accessed without using a setter or getter.

More about CWE-608 definition and examples

Related CWE

CWE-609: Double-Checked Locking

  • Status: Draft
  • Weakness Abstractions: Base

The program uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient.

More about CWE-609 definition and examples

Related CWE

CWE-610: Externally Controlled Reference to a Resource in Another Sphere

  • Status: Draft
  • Weakness Abstractions: Class

The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.

More about CWE-610 definition and examples

Related CWE

CWE-611: Improper Restriction of XML External Entity Reference

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-611 definition and examples

Related CWE

CWE-612: Improper Authorization of Index Containing Sensitive Information

  • Status: Draft
  • Weakness Abstractions: Base

The product creates a search index of private or sensitive documents, but it does not properly limit index access to actors who are authorized to see the original information.

More about CWE-612 definition and examples

Related CWE

CWE-613: Insufficient Session Expiration

  • Status: Incomplete
  • Weakness Abstractions: Base

According to WASC, “Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.”

More about CWE-613 definition and examples

Related CWE

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-614 definition and examples

Related CWE

CWE-615: Inclusion of Sensitive Information in Source Code Comments

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-615 definition and examples

Related CWE

CWE-616: Incomplete Identification of Uploaded File Variables (PHP)

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-616 definition and examples

Related CWE

CWE-617: Reachable Assertion

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-617 definition and examples

Related CWE

CWE-618: Exposed Unsafe ActiveX Method

  • Status: Incomplete
  • Weakness Abstractions: Base

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).

More about CWE-618 definition and examples

Related CWE

CWE-619: Dangling Database Cursor (‘Cursor Injection’)

  • Status: Incomplete
  • Weakness Abstractions: Base

This could be primary when the programmer never attempts to close the cursor when finished with it.

More about CWE-619 definition and examples

Related CWE

CWE-620: Unverified Password Change

  • Status: Draft
  • Weakness Abstractions: Base

When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.

More about CWE-620 definition and examples

Related CWE

CWE-621: Variable Extraction Error

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-621 definition and examples

Related CWE

CWE-622: Improper Validation of Function Hook Arguments

  • Status: Draft
  • Weakness Abstractions: Variant

The product adds hooks to user-accessible API functions, but it does not properly validate the arguments. This could lead to resultant vulnerabilities.

More about CWE-622 definition and examples

Related CWE

CWE-623: Unsafe ActiveX Control Marked Safe For Scripting

  • Status: Draft
  • Weakness Abstractions: Variant

An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.

More about CWE-623 definition and examples

Related CWE

CWE-624: Executable Regular Expression Error

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-624 definition and examples

Related CWE

CWE-625: Permissive Regular Expression

  • Status: Draft
  • Weakness Abstractions: Base

The product uses a regular expression that does not sufficiently restrict the set of allowed values.

More about CWE-625 definition and examples

Related CWE

CWE-626: Null Byte Interaction Error (Poison Null Byte)

  • Status: Draft
  • Weakness Abstractions: Variant

The product does not properly handle null bytes or NUL characters when passing data between different representations or components.

More about CWE-626 definition and examples

Related CWE

CWE-627: Dynamic Variable Evaluation

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-627 definition and examples

Related CWE

CWE-628: Function Call with Incorrectly Specified Arguments

  • Status: Draft
  • Weakness Abstractions: Base

This is usually primary to other weaknesses, but it can be resultant if the function’s API or function prototype changes.

More about CWE-628 definition and examples

Related CWE

CWE-636: Not Failing Securely (‘Failing Open’)

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-636 definition and examples

Related CWE

CWE-637: Unnecessary Complexity in Protection Mechanism (Not Using ‘Economy of Mechanism’)

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-637 definition and examples

Related CWE

CWE-638: Not Using Complete Mediation

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-638 definition and examples

Related CWE

CWE-639: Authorization Bypass Through User-Controlled Key

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-639 definition and examples

Related CWE

CWE-640: Weak Password Recovery Mechanism for Forgotten Password

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.

More about CWE-640 definition and examples

Related CWE

CWE-641: Improper Restriction of Names for Files and Other Resources

  • Status: Incomplete
  • Weakness Abstractions: Base

The application constructs the name of a file or other resource using input from an upstream component, but it does not restrict or incorrectly restricts the resulting name.

More about CWE-641 definition and examples

Related CWE

CWE-642: External Control of Critical State Data

  • Status: Draft
  • Weakness Abstractions: Class

The software stores security-critical state information about its users, or the software itself, in a location that is accessible to unauthorized actors.

More about CWE-642 definition and examples

Related CWE

CWE-643: Improper Neutralization of Data within XPath Expressions (‘XPath Injection’)

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-643 definition and examples

Related CWE

CWE-644: Improper Neutralization of HTTP Headers for Scripting Syntax

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-644 definition and examples

Related CWE

CWE-645: Overly Restrictive Account Lockout Mechanism

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains an account lockout protection mechanism, but the mechanism is too restrictive and can be triggered too easily, which allows attackers to deny service to legitimate users by causing their accounts to be locked out.

More about CWE-645 definition and examples

Related CWE

CWE-646: Reliance on File Name or Extension of Externally-Supplied File

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-646 definition and examples

Related CWE

CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-647 definition and examples

Related CWE

CWE-648: Incorrect Use of Privileged APIs

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-648 definition and examples

Related CWE

CWE-649: Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-649 definition and examples

Related CWE

CWE-650: Trusting HTTP Permission Methods on the Server Side

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-650 definition and examples

Related CWE

CWE-651: Exposure of WSDL File Containing Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Variant

The Web services architecture may require exposing a Web Service Definition Language (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).

More about CWE-651 definition and examples

Related CWE

CWE-652: Improper Neutralization of Data within XQuery Expressions (‘XQuery Injection’)

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-652 definition and examples

Related CWE

CWE-653: Insufficient Compartmentalization

  • Status: Draft
  • Weakness Abstractions: Base

The product does not sufficiently compartmentalize functionality or processes that require different privilege levels, rights, or permissions.

More about CWE-653 definition and examples

Related CWE

CWE-654: Reliance on a Single Factor in a Security Decision

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-654 definition and examples

Related CWE

CWE-655: Insufficient Psychological Acceptability

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-655 definition and examples

Related CWE

CWE-656: Reliance on Security Through Obscurity

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-656 definition and examples

Related CWE

CWE-657: Violation of Secure Design Principles

  • Status: Draft
  • Weakness Abstractions: Class

The product violates well-established principles for secure design.

More about CWE-657 definition and examples

Related CWE

CWE-662: Improper Synchronization

  • Status: Draft
  • Weakness Abstractions: Class

The software utilizes multiple threads or processes to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.

More about CWE-662 definition and examples

Related CWE

CWE-663: Use of a Non-reentrant Function in a Concurrent Context

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-663 definition and examples

Related CWE

CWE-664: Improper Control of a Resource Through its Lifetime

  • Status: Draft
  • Weakness Abstractions: Pillar

The software does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.

More about CWE-664 definition and examples

CWE-665: Improper Initialization

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-665 definition and examples

Related CWE

CWE-666: Operation on Resource in Wrong Phase of Lifetime

  • Status: Draft
  • Weakness Abstractions: Class

The software performs an operation on a resource at the wrong phase of the resource’s lifecycle, which can lead to unexpected behaviors.

More about CWE-666 definition and examples

Related CWE

CWE-667: Improper Locking

  • Status: Draft
  • Weakness Abstractions: Class

The software does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

More about CWE-667 definition and examples

Related CWE

CWE-668: Exposure of Resource to Wrong Sphere

  • Status: Draft
  • Weakness Abstractions: Class

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

More about CWE-668 definition and examples

Related CWE

CWE-669: Incorrect Resource Transfer Between Spheres

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-669 definition and examples

Related CWE

CWE-670: Always-Incorrect Control Flow Implementation

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-670 definition and examples

Related CWE

CWE-671: Lack of Administrator Control over Security

  • Status: Draft
  • Weakness Abstractions: Class

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.

More about CWE-671 definition and examples

Related CWE

CWE-672: Operation on a Resource after Expiration or Release

  • Status: Draft
  • Weakness Abstractions: Class

The software uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.

More about CWE-672 definition and examples

Related CWE

CWE-673: External Influence of Sphere Definition

  • Status: Draft
  • Weakness Abstractions: Class

The product does not prevent the definition of control spheres from external actors.

More about CWE-673 definition and examples

Related CWE

CWE-674: Uncontrolled Recursion

  • Status: Draft
  • Weakness Abstractions: Class

The product does not properly control the amount of recursion which takes place, consuming excessive resources, such as allocated memory or the program stack.

More about CWE-674 definition and examples

Related CWE

CWE-675: Duplicate Operations on Resource

  • Status: Draft
  • Weakness Abstractions: Class

The product performs the same operation on a resource two or more times, when the operation should only be applied once.

More about CWE-675 definition and examples

Related CWE

CWE-676: Use of Potentially Dangerous Function

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-676 definition and examples

Related CWE

CWE-680: Integer Overflow to Buffer Overflow

  • Status: Draft
  • Weakness Abstractions: Compound

The product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow.

More about CWE-680 definition and examples

Related CWE

CWE-681: Incorrect Conversion between Numeric Types

  • Status: Draft
  • Weakness Abstractions: Base

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.

More about CWE-681 definition and examples

Related CWE

CWE-682: Incorrect Calculation

  • Status: Draft
  • Weakness Abstractions: Pillar

The software performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.

More about CWE-682 definition and examples

Related CWE

CWE-683: Function Call With Incorrect Order of Arguments

  • Status: Draft
  • Weakness Abstractions: Variant

The software calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses.

More about CWE-683 definition and examples

Related CWE

CWE-684: Incorrect Provision of Specified Functionality

  • Status: Draft
  • Weakness Abstractions: Class

The code does not function according to its published specifications, potentially leading to incorrect usage.

More about CWE-684 definition and examples

Related CWE

CWE-685: Function Call With Incorrect Number of Arguments

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-685 definition and examples

Related CWE

CWE-686: Function Call With Incorrect Argument Type

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-686 definition and examples

Related CWE

CWE-687: Function Call With Incorrectly Specified Argument Value

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-687 definition and examples

Related CWE

CWE-688: Function Call With Incorrect Variable or Reference as Argument

  • Status: Draft
  • Weakness Abstractions: Variant

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.

More about CWE-688 definition and examples

Related CWE

CWE-689: Permission Race Condition During Resource Copy

  • Status: Draft
  • Weakness Abstractions: Compound

The product, while copying or cloning a resource, does not set the resource’s permissions or access control until the copy is complete, leaving the resource exposed to other spheres while the copy is taking place.

More about CWE-689 definition and examples

Related CWE

CWE-690: Unchecked Return Value to NULL Pointer Dereference

  • Status: Draft
  • Weakness Abstractions: Compound

The product does not check for an error after calling a function that can return with a NULL pointer if the function fails, which leads to a resultant NULL pointer dereference.

More about CWE-690 definition and examples

Related CWE

CWE-691: Insufficient Control Flow Management

  • Status: Draft
  • Weakness Abstractions: Pillar

The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways.

More about CWE-691 definition and examples

CWE-692: Incomplete Denylist to Cross-Site Scripting

  • Status: Draft
  • Weakness Abstractions: Compound

The product uses a denylist-based protection mechanism to defend against XSS attacks, but the denylist is incomplete, allowing XSS variants to succeed.

More about CWE-692 definition and examples

Related CWE

CWE-693: Protection Mechanism Failure

  • Status: Draft
  • Weakness Abstractions: Pillar

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

More about CWE-693 definition and examples

CWE-694: Use of Multiple Resources with Duplicate Identifier

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.

More about CWE-694 definition and examples

Related CWE

CWE-695: Use of Low-Level Functionality

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses low-level functionality that is explicitly prohibited by the framework or specification under which the software is supposed to operate.

More about CWE-695 definition and examples

Related CWE

CWE-696: Incorrect Behavior Order

  • Status: Incomplete
  • Weakness Abstractions: Class

The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways which may produce resultant weaknesses.

More about CWE-696 definition and examples

Related CWE

CWE-697: Incorrect Comparison

  • Status: Incomplete
  • Weakness Abstractions: Pillar

The software compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses.

More about CWE-697 definition and examples

CWE-698: Execution After Redirect (EAR)

  • Status: Incomplete
  • Weakness Abstractions: Base

The web application sends a redirect to another location, but instead of exiting, it executes additional code.

More about CWE-698 definition and examples

Related CWE

CWE-703: Improper Check or Handling of Exceptional Conditions

  • Status: Incomplete
  • Weakness Abstractions: Pillar

The software does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the software.

More about CWE-703 definition and examples

CWE-704: Incorrect Type Conversion or Cast

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not correctly convert an object, resource, or structure from one type to a different type.

More about CWE-704 definition and examples

Related CWE

CWE-705: Incorrect Control Flow Scoping

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not properly return control flow to the proper location after it has completed a task or detected an unusual condition.

More about CWE-705 definition and examples

Related CWE

CWE-706: Use of Incorrectly-Resolved Name or Reference

  • Status: Incomplete
  • Weakness Abstractions: Class

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.

More about CWE-706 definition and examples

Related CWE

CWE-707: Improper Neutralization

  • Status: Incomplete
  • Weakness Abstractions: Pillar

The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component.

More about CWE-707 definition and examples

CWE-708: Incorrect Ownership Assignment

  • Status: Incomplete
  • Weakness Abstractions: Base

This entry has been deprecated as it represents a specific observed example of a UNIX Hard Link weakness type rather than its own individual weakness type. Please refer to CWE-62.

More about CWE-708 definition and examples

Related CWE

CWE-710: Improper Adherence to Coding Standards

  • Status: Incomplete
  • Weakness Abstractions: Pillar

The software does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.

More about CWE-710 definition and examples

CWE-712: OWASP Top Ten 2007 Category A1 - Cross Site Scripting (XSS)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2007.

More about CWE-712 definition and examples

CWE-713: OWASP Top Ten 2007 Category A2 - Injection Flaws

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2007.

More about CWE-713 definition and examples

CWE-714: OWASP Top Ten 2007 Category A3 - Malicious File Execution

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2007.

More about CWE-714 definition and examples

CWE-715: OWASP Top Ten 2007 Category A4 - Insecure Direct Object Reference

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2007.

More about CWE-715 definition and examples

CWE-716: OWASP Top Ten 2007 Category A5 - Cross Site Request Forgery (CSRF)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2007.

More about CWE-716 definition and examples

CWE-717: OWASP Top Ten 2007 Category A6 - Information Leakage and Improper Error Handling

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2007.

More about CWE-717 definition and examples

CWE-718: OWASP Top Ten 2007 Category A7 - Broken Authentication and Session Management

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2007.

More about CWE-718 definition and examples

CWE-719: OWASP Top Ten 2007 Category A8 - Insecure Cryptographic Storage

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2007.

More about CWE-719 definition and examples

CWE-720: OWASP Top Ten 2007 Category A9 - Insecure Communications

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2007.

More about CWE-720 definition and examples

CWE-721: OWASP Top Ten 2007 Category A10 - Failure to Restrict URL Access

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2007.

More about CWE-721 definition and examples

CWE-722: OWASP Top Ten 2004 Category A1 - Unvalidated Input

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2004.

More about CWE-722 definition and examples

CWE-723: OWASP Top Ten 2004 Category A2 - Broken Access Control

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2004.

More about CWE-723 definition and examples

CWE-724: OWASP Top Ten 2004 Category A3 - Broken Authentication and Session Management

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2004.

More about CWE-724 definition and examples

CWE-725: OWASP Top Ten 2004 Category A4 - Cross-Site Scripting (XSS) Flaws

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2004.

More about CWE-725 definition and examples

CWE-726: OWASP Top Ten 2004 Category A5 - Buffer Overflows

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2004.

More about CWE-726 definition and examples

CWE-727: OWASP Top Ten 2004 Category A6 - Injection Flaws

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2004.

More about CWE-727 definition and examples

CWE-728: OWASP Top Ten 2004 Category A7 - Improper Error Handling

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2004.

More about CWE-728 definition and examples

CWE-729: OWASP Top Ten 2004 Category A8 - Insecure Storage

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2004.

More about CWE-729 definition and examples

CWE-730: OWASP Top Ten 2004 Category A9 - Denial of Service

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2004.

More about CWE-730 definition and examples

CWE-731: OWASP Top Ten 2004 Category A10 - Insecure Configuration Management

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2004.

More about CWE-731 definition and examples

CWE-732: Incorrect Permission Assignment for Critical Resource

  • Status: Draft
  • Weakness Abstractions: Class

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

More about CWE-732 definition and examples

Related CWE

CWE-733: Compiler Optimization Removal or Modification of Security-critical Code

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-733 definition and examples

Related CWE

CWE-735: CERT C Secure Coding Standard (2008) Chapter 2 - Preprocessor (PRE)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Preprocessor (PRE) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-735 definition and examples

CWE-736: CERT C Secure Coding Standard (2008) Chapter 3 - Declarations and Initialization (DCL)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-736 definition and examples

CWE-737: CERT C Secure Coding Standard (2008) Chapter 4 - Expressions (EXP)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-737 definition and examples

CWE-738: CERT C Secure Coding Standard (2008) Chapter 5 - Integers (INT)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Integers (INT) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-738 definition and examples

CWE-739: CERT C Secure Coding Standard (2008) Chapter 6 - Floating Point (FLP)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Floating Point (FLP) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-739 definition and examples

CWE-740: CERT C Secure Coding Standard (2008) Chapter 7 - Arrays (ARR)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Arrays (ARR) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-740 definition and examples

CWE-741: CERT C Secure Coding Standard (2008) Chapter 8 - Characters and Strings (STR)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Characters and Strings (STR) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-741 definition and examples

CWE-742: CERT C Secure Coding Standard (2008) Chapter 9 - Memory Management (MEM)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Memory Management (MEM) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-742 definition and examples

CWE-743: CERT C Secure Coding Standard (2008) Chapter 10 - Input Output (FIO)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Input Output (FIO) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-743 definition and examples

CWE-744: CERT C Secure Coding Standard (2008) Chapter 11 - Environment (ENV)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Environment (ENV) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-744 definition and examples

CWE-745: CERT C Secure Coding Standard (2008) Chapter 12 - Signals (SIG)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Signals (SIG) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-745 definition and examples

CWE-746: CERT C Secure Coding Standard (2008) Chapter 13 - Error Handling (ERR)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Error Handling (ERR) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-746 definition and examples

CWE-747: CERT C Secure Coding Standard (2008) Chapter 14 - Miscellaneous (MSC)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) chapter of the CERT C Secure Coding Standard (2008).

More about CWE-747 definition and examples

CWE-748: CERT C Secure Coding Standard (2008) Appendix - POSIX (POS)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the POSIX (POS) appendix of the CERT C Secure Coding Standard (2008).

More about CWE-748 definition and examples

CWE-749: Exposed Dangerous Method or Function

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-749 definition and examples

Related CWE

CWE-751: 2009 Top 25 - Insecure Interaction Between Components

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are listed in the “Insecure Interaction Between Components” section of the 2009 CWE/SANS Top 25 Programming Errors.

More about CWE-751 definition and examples

CWE-752: 2009 Top 25 - Risky Resource Management

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are listed in the “Risky Resource Management” section of the 2009 CWE/SANS Top 25 Programming Errors.

More about CWE-752 definition and examples

CWE-753: 2009 Top 25 - Porous Defenses

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are listed in the “Porous Defenses” section of the 2009 CWE/SANS Top 25 Programming Errors.

More about CWE-753 definition and examples

CWE-754: Improper Check for Unusual or Exceptional Conditions

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the software.

More about CWE-754 definition and examples

Related CWE

CWE-755: Improper Handling of Exceptional Conditions

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not handle or incorrectly handles an exceptional condition.

More about CWE-755 definition and examples

Related CWE

CWE-756: Missing Custom Error Page

  • Status: Incomplete
  • Weakness Abstractions: Base

The software does not return custom error pages to the user, possibly exposing sensitive information.

More about CWE-756 definition and examples

Related CWE

CWE-757: Selection of Less-Secure Algorithm During Negotiation (‘Algorithm Downgrade’)

  • Status: Incomplete
  • Weakness Abstractions: Base

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.

More about CWE-757 definition and examples

Related CWE

CWE-758: Reliance on Undefined, Unspecified, or Implementation-Defined Behavior

  • Status: Incomplete
  • Weakness Abstractions: Class

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.

More about CWE-758 definition and examples

Related CWE

CWE-759: Use of a One-Way Hash without a Salt

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-759 definition and examples

Related CWE

CWE-760: Use of a One-Way Hash with a Predictable Salt

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-760 definition and examples

Related CWE

CWE-761: Free of Pointer not at Start of Buffer

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-761 definition and examples

Related CWE

CWE-762: Mismatched Memory Management Routines

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-762 definition and examples

Related CWE

CWE-763: Release of Invalid Pointer or Reference

  • Status: Incomplete
  • Weakness Abstractions: Base

The application attempts to return a memory resource to the system, but calls the wrong release function or calls the appropriate release function incorrectly.

More about CWE-763 definition and examples

Related CWE

CWE-764: Multiple Locks of a Critical Resource

  • Status: Incomplete
  • Weakness Abstractions: Base

The software locks a critical resource more times than intended, leading to an unexpected state in the system.

More about CWE-764 definition and examples

Related CWE

CWE-765: Multiple Unlocks of a Critical Resource

  • Status: Incomplete
  • Weakness Abstractions: Base

The software unlocks a critical resource more times than intended, leading to an unexpected state in the system.

More about CWE-765 definition and examples

Related CWE

CWE-766: Critical Data Element Declared Public

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software declares a critical variable, field, or member to be public when intended security policy requires it to be private.

More about CWE-766 definition and examples

Related CWE

CWE-767: Access to Critical Private Variable via Public Method

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software defines a public method that reads or modifies a private variable.

More about CWE-767 definition and examples

Related CWE

CWE-768: Incorrect Short Circuit Evaluation

  • Status: Incomplete
  • Weakness Abstractions: Variant

This entry has been deprecated because it was a duplicate of CWE-774. All content has been transferred to CWE-774.

More about CWE-768 definition and examples

Related CWE

CWE-770: Allocation of Resources Without Limits or Throttling

  • Status: Incomplete
  • Weakness Abstractions: Base

The software allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.

More about CWE-770 definition and examples

Related CWE

CWE-771: Missing Reference to Active Allocated Resource

  • Status: Incomplete
  • Weakness Abstractions: Base

The software does not properly maintain a reference to a resource that has been allocated, which prevents the resource from being reclaimed.

More about CWE-771 definition and examples

Related CWE

CWE-772: Missing Release of Resource after Effective Lifetime

  • Status: Draft
  • Weakness Abstractions: Base

The software does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

More about CWE-772 definition and examples

Related CWE

CWE-773: Missing Reference to Active File Descriptor or Handle

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software does not properly maintain references to a file descriptor or handle, which prevents that file descriptor/handle from being reclaimed.

More about CWE-773 definition and examples

Related CWE

CWE-774: Allocation of File Descriptors or Handles Without Limits or Throttling

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-774 definition and examples

Related CWE

CWE-775: Missing Release of File Descriptor or Handle after Effective Lifetime

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-775 definition and examples

Related CWE

CWE-776: Improper Restriction of Recursive Entity References in DTDs (‘XML Entity Expansion’)

  • Status: Draft
  • Weakness Abstractions: Base

The software uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities.

More about CWE-776 definition and examples

Related CWE

CWE-777: Regular Expression without Anchors

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software uses a regular expression to perform neutralization, but the regular expression is not anchored and may allow malicious or malformed data to slip through.

More about CWE-777 definition and examples

Related CWE

CWE-778: Insufficient Logging

  • Status: Draft
  • Weakness Abstractions: Base

When a security-critical event occurs, the software either does not record the event or omits important details about the event when logging it.

More about CWE-778 definition and examples

Related CWE

CWE-779: Logging of Excessive Data

  • Status: Draft
  • Weakness Abstractions: Base

The software logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack.

More about CWE-779 definition and examples

Related CWE

CWE-780: Use of RSA Algorithm without OAEP

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software uses the RSA algorithm but does not incorporate Optimal Asymmetric Encryption Padding (OAEP), which might weaken the encryption.

More about CWE-780 definition and examples

Related CWE

CWE-781: Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code

  • Status: Draft
  • Weakness Abstractions: Variant

The software defines an IOCTL that uses METHOD_NEITHER for I/O, but it does not validate or incorrectly validates the addresses that are provided.

More about CWE-781 definition and examples

Related CWE

CWE-782: Exposed IOCTL with Insufficient Access Control

  • Status: Draft
  • Weakness Abstractions: Variant

The software implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.

More about CWE-782 definition and examples

Related CWE

CWE-783: Operator Precedence Logic Error

  • Status: Draft
  • Weakness Abstractions: Base

The program uses an expression in which operator precedence causes incorrect logic to be used.

More about CWE-783 definition and examples

Related CWE

CWE-784: Reliance on Cookies without Validation and Integrity Checking in a Security Decision

  • Status: Draft
  • Weakness Abstractions: Variant

The application uses a protection mechanism that relies on the existence or values of a cookie, but it does not properly ensure that the cookie is valid for the associated user.

More about CWE-784 definition and examples

Related CWE

CWE-785: Use of Path Manipulation Function without Maximum-sized Buffer

  • Status: Incomplete
  • Weakness Abstractions: Variant

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.

More about CWE-785 definition and examples

Related CWE

CWE-786: Access of Memory Location Before Start of Buffer

  • Status: Incomplete
  • Weakness Abstractions: Base

The software reads or writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.

More about CWE-786 definition and examples

Related CWE

CWE-787: Out-of-bounds Write

  • Status: Draft
  • Weakness Abstractions: Base

The software writes data past the end, or before the beginning, of the intended buffer.

More about CWE-787 definition and examples

Related CWE

CWE-788: Access of Memory Location After End of Buffer

  • Status: Incomplete
  • Weakness Abstractions: Base

The software reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer.

More about CWE-788 definition and examples

Related CWE

CWE-789: Memory Allocation with Excessive Size Value

  • Status: Draft
  • Weakness Abstractions: Variant

The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

More about CWE-789 definition and examples

Related CWE

CWE-790: Improper Filtering of Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Class

The software receives data from an upstream component, but does not filter or incorrectly filters special elements before sending it to a downstream component.

More about CWE-790 definition and examples

Related CWE

CWE-791: Incomplete Filtering of Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Base

The software receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.

More about CWE-791 definition and examples

Related CWE

CWE-792: Incomplete Filtering of One or More Instances of Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software receives data from an upstream component, but does not completely filter one or more instances of special elements before sending it to a downstream component.

More about CWE-792 definition and examples

Related CWE

CWE-793: Only Filtering One Instance of a Special Element

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software receives data from an upstream component, but only filters a single instance of a special element before sending it to a downstream component.

More about CWE-793 definition and examples

Related CWE

CWE-794: Incomplete Filtering of Multiple Instances of Special Elements

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software receives data from an upstream component, but does not filter all instances of a special element before sending it to a downstream component.

More about CWE-794 definition and examples

Related CWE

CWE-795: Only Filtering Special Elements at a Specified Location

  • Status: Incomplete
  • Weakness Abstractions: Base

The software receives data from an upstream component, but only accounts for special elements at a specified location, thereby missing remaining special elements that may exist before sending it to a downstream component.

More about CWE-795 definition and examples

Related CWE

CWE-796: Only Filtering Special Elements Relative to a Marker

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software receives data from an upstream component, but only accounts for special elements positioned relative to a marker (e.g. “at the beginning/end of a string; the second argument”), thereby missing remaining special elements that may exist before sending it to a downstream component.

More about CWE-796 definition and examples

Related CWE

CWE-797: Only Filtering Special Elements at an Absolute Position

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software receives data from an upstream component, but only accounts for special elements at an absolute position (e.g. “byte number 10”), thereby missing remaining special elements that may exist before sending it to a downstream component.

More about CWE-797 definition and examples

Related CWE

CWE-798: Use of Hard-coded Credentials

  • Status: Draft
  • Weakness Abstractions: Base

The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.

More about CWE-798 definition and examples

Related CWE

CWE-799: Improper Control of Interaction Frequency

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests.

More about CWE-799 definition and examples

Related CWE

CWE-801: 2010 Top 25 - Insecure Interaction Between Components

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are listed in the “Insecure Interaction Between Components” section of the 2010 CWE/SANS Top 25 Programming Errors.

More about CWE-801 definition and examples

CWE-802: 2010 Top 25 - Risky Resource Management

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are listed in the “Risky Resource Management” section of the 2010 CWE/SANS Top 25 Programming Errors.

More about CWE-802 definition and examples

CWE-803: 2010 Top 25 - Porous Defenses

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are listed in the “Porous Defenses” section of the 2010 CWE/SANS Top 25 Programming Errors.

More about CWE-803 definition and examples

CWE-804: Guessable CAPTCHA

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a CAPTCHA challenge, but the challenge can be guessed or automatically recognized by a non-human actor.

More about CWE-804 definition and examples

Related CWE

CWE-805: Buffer Access with Incorrect Length Value

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer.

More about CWE-805 definition and examples

Related CWE

CWE-806: Buffer Access Using Size of Source Buffer

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software uses the size of a source buffer when reading from or writing to a destination buffer, which may cause it to access memory that is outside of the bounds of the buffer.

More about CWE-806 definition and examples

Related CWE

CWE-807: Reliance on Untrusted Inputs in a Security Decision

  • Status: Incomplete
  • Weakness Abstractions: Base

The application uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism.

More about CWE-807 definition and examples

Related CWE

CWE-808: 2010 Top 25 - Weaknesses On the Cusp

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are not part of the general Top 25, but they were part of the original nominee list from which the Top 25 was drawn.

More about CWE-808 definition and examples

CWE-810: OWASP Top Ten 2010 Category A1 - Injection

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2010.

More about CWE-810 definition and examples

CWE-811: OWASP Top Ten 2010 Category A2 - Cross-Site Scripting (XSS)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2010.

More about CWE-811 definition and examples

CWE-812: OWASP Top Ten 2010 Category A3 - Broken Authentication and Session Management

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2010.

More about CWE-812 definition and examples

CWE-813: OWASP Top Ten 2010 Category A4 - Insecure Direct Object References

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2010.

More about CWE-813 definition and examples

CWE-814: OWASP Top Ten 2010 Category A5 - Cross-Site Request Forgery(CSRF)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2010.

More about CWE-814 definition and examples

CWE-815: OWASP Top Ten 2010 Category A6 - Security Misconfiguration

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2010.

More about CWE-815 definition and examples

CWE-816: OWASP Top Ten 2010 Category A7 - Insecure Cryptographic Storage

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2010.

More about CWE-816 definition and examples

CWE-817: OWASP Top Ten 2010 Category A8 - Failure to Restrict URL Access

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2010.

More about CWE-817 definition and examples

CWE-818: OWASP Top Ten 2010 Category A9 - Insufficient Transport Layer Protection

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2010.

More about CWE-818 definition and examples

CWE-819: OWASP Top Ten 2010 Category A10 - Unvalidated Redirects and Forwards

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2010.

More about CWE-819 definition and examples

CWE-820: Missing Synchronization

  • Status: Incomplete
  • Weakness Abstractions: Base

The software utilizes a shared resource in a concurrent manner but does not attempt to synchronize access to the resource.

More about CWE-820 definition and examples

Related CWE

CWE-821: Incorrect Synchronization

  • Status: Incomplete
  • Weakness Abstractions: Base

The software utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.

More about CWE-821 definition and examples

Related CWE

CWE-822: Untrusted Pointer Dereference

  • Status: Incomplete
  • Weakness Abstractions: Base

The program obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.

More about CWE-822 definition and examples

Related CWE

CWE-823: Use of Out-of-range Pointer Offset

  • Status: Incomplete
  • Weakness Abstractions: Base

The program performs pointer arithmetic on a valid pointer, but it uses an offset that can point outside of the intended range of valid memory locations for the resulting pointer.

More about CWE-823 definition and examples

Related CWE

CWE-824: Access of Uninitialized Pointer

  • Status: Incomplete
  • Weakness Abstractions: Base

The program accesses or uses a pointer that has not been initialized.

More about CWE-824 definition and examples

Related CWE

CWE-825: Expired Pointer Dereference

  • Status: Incomplete
  • Weakness Abstractions: Base

The program dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

More about CWE-825 definition and examples

Related CWE

CWE-826: Premature Release of Resource During Expected Lifetime

  • Status: Incomplete
  • Weakness Abstractions: Base

The program releases a resource that is still intended to be used by the program itself or another actor.

More about CWE-826 definition and examples

Related CWE

CWE-827: Improper Control of Document Type Definition

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software does not restrict a reference to a Document Type Definition (DTD) to the intended control sphere. This might allow attackers to reference arbitrary DTDs, possibly causing the software to expose files, consume excessive system resources, or execute arbitrary http requests on behalf of the attacker.

More about CWE-827 definition and examples

Related CWE

CWE-828: Signal Handler with Functionality that is not Asynchronous-Safe

  • Status: Incomplete
  • Weakness Abstractions: Base

The software defines a signal handler that contains code sequences that are not asynchronous-safe, i.e., the functionality is not reentrant, or it can be interrupted.

More about CWE-828 definition and examples

Related CWE

CWE-829: Inclusion of Functionality from Untrusted Control Sphere

  • Status: Incomplete
  • Weakness Abstractions: Base

The software imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.

More about CWE-829 definition and examples

Related CWE

CWE-830: Inclusion of Web Functionality from an Untrusted Source

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software includes web functionality (such as a web widget) from another domain, which causes it to operate within the domain of the software, potentially granting total access and control of the software to the untrusted source.

More about CWE-830 definition and examples

Related CWE

CWE-831: Signal Handler Function Associated with Multiple Signals

  • Status: Incomplete
  • Weakness Abstractions: Base

The software defines a function that is used as a handler for more than one signal.

More about CWE-831 definition and examples

Related CWE

CWE-832: Unlock of a Resource that is not Locked

  • Status: Incomplete
  • Weakness Abstractions: Base

The software attempts to unlock a resource that is not locked.

More about CWE-832 definition and examples

Related CWE

CWE-833: Deadlock

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.

More about CWE-833 definition and examples

Related CWE

CWE-834: Excessive Iteration

  • Status: Incomplete
  • Weakness Abstractions: Class

The software performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.

More about CWE-834 definition and examples

Related CWE

CWE-835: Loop with Unreachable Exit Condition (‘Infinite Loop’)

  • Status: Incomplete
  • Weakness Abstractions: Base

The program contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

More about CWE-835 definition and examples

Related CWE

CWE-836: Use of Password Hash Instead of Password for Authentication

  • Status: Incomplete
  • Weakness Abstractions: Base

The software records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store.

More about CWE-836 definition and examples

Related CWE

CWE-837: Improper Enforcement of a Single, Unique Action

  • Status: Incomplete
  • Weakness Abstractions: Base

The software requires that an actor should only be able to perform an action once, or to have only one unique action, but the software does not enforce or improperly enforces this restriction.

More about CWE-837 definition and examples

Related CWE

CWE-838: Inappropriate Encoding for Output Context

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component.

More about CWE-838 definition and examples

Related CWE

CWE-839: Numeric Range Comparison Without Minimum Check

  • Status: Incomplete
  • Weakness Abstractions: Base

The program checks a value to ensure that it is less than or equal to a maximum, but it does not also verify that the value is greater than or equal to the minimum.

More about CWE-839 definition and examples

Related CWE

CWE-840: Business Logic Errors

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category identify some of the underlying problems that commonly allow attackers to manipulate the business logic of an application. Errors in business logic can be devastating to an entire application. They can be difficult to find automatically, since they typically involve legitimate use of the application’s functionality. However, many business logic errors can exhibit patterns that are similar to well-understood implementation and design weaknesses.

More about CWE-840 definition and examples

CWE-841: Improper Enforcement of Behavioral Workflow

  • Status: Incomplete
  • Weakness Abstractions: Base

The software supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence.

More about CWE-841 definition and examples

Related CWE

CWE-842: Placement of User into Incorrect Group

  • Status: Incomplete
  • Weakness Abstractions: Base

The software or the administrator places a user into an incorrect group.

More about CWE-842 definition and examples

Related CWE

CWE-843: Access of Resource Using Incompatible Type (‘Type Confusion’)

  • Status: Incomplete
  • Weakness Abstractions: Base

The program allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.

More about CWE-843 definition and examples

Related CWE

CWE-845: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 2 - Input Validation and Data Sanitization (IDS)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Input Validation and Data Sanitization (IDS) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-845 definition and examples

CWE-846: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 3 - Declarations and Initialization (DCL)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Declarations and Initialization (DCL) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-846 definition and examples

CWE-847: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 4 - Expressions (EXP)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Expressions (EXP) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-847 definition and examples

CWE-848: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 5 - Numeric Types and Operations (NUM)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Numeric Types and Operations (NUM) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-848 definition and examples

CWE-849: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 6 - Object Orientation (OBJ)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Object Orientation (OBJ) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-849 definition and examples

CWE-850: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 7 - Methods (MET)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Methods (MET) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-850 definition and examples

CWE-851: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 8 - Exceptional Behavior (ERR)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Exceptional Behavior (ERR) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-851 definition and examples

CWE-852: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 9 - Visibility and Atomicity (VNA)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Visibility and Atomicity (VNA) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-852 definition and examples

CWE-853: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 10 - Locking (LCK)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Locking (LCK) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-853 definition and examples

CWE-854: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 11 - Thread APIs (THI)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Thread APIs (THI) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-854 definition and examples

CWE-855: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 12 - Thread Pools (TPS)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Thread Pools (TPS) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-855 definition and examples

CWE-856: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 13 - Thread-Safety Miscellaneous (TSM)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Thread-Safety Miscellaneous (TSM) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-856 definition and examples

CWE-857: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 14 - Input Output (FIO)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Input Output (FIO) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-857 definition and examples

CWE-858: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 15 - Serialization (SER)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Serialization (SER) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-858 definition and examples

CWE-859: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 16 - Platform Security (SEC)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Platform Security (SEC) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-859 definition and examples

CWE-860: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 17 - Runtime Environment (ENV)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Runtime Environment (ENV) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-860 definition and examples

CWE-861: The CERT Oracle Secure Coding Standard for Java (2011) Chapter 18 - Miscellaneous (MSC)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Miscellaneous (MSC) chapter of The CERT Oracle Secure Coding Standard for Java (2011).

More about CWE-861 definition and examples

CWE-862: Missing Authorization

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not perform an authorization check when an actor attempts to access a resource or perform an action.

More about CWE-862 definition and examples

Related CWE

CWE-863: Incorrect Authorization

  • Status: Incomplete
  • Weakness Abstractions: Class

The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.

More about CWE-863 definition and examples

Related CWE

CWE-864: 2011 Top 25 - Insecure Interaction Between Components

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are listed in the “Insecure Interaction Between Components” section of the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.

More about CWE-864 definition and examples

CWE-865: 2011 Top 25 - Risky Resource Management

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are listed in the “Risky Resource Management” section of the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.

More about CWE-865 definition and examples

CWE-866: 2011 Top 25 - Porous Defenses

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are listed in the “Porous Defenses” section of the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.

More about CWE-866 definition and examples

CWE-867: 2011 Top 25 - Weaknesses On the Cusp

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are not part of the general Top 25, but they were part of the original nominee list from which the Top 25 was drawn.

More about CWE-867 definition and examples

CWE-869: CERT C++ Secure Coding Section 01 - Preprocessor (PRE)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Preprocessor (PRE) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-869 definition and examples

CWE-870: CERT C++ Secure Coding Section 02 - Declarations and Initialization (DCL)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Declarations and Initialization (DCL) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-870 definition and examples

CWE-871: CERT C++ Secure Coding Section 03 - Expressions (EXP)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Expressions (EXP) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-871 definition and examples

CWE-872: CERT C++ Secure Coding Section 04 - Integers (INT)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Integers (INT) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-872 definition and examples

CWE-873: CERT C++ Secure Coding Section 05 - Floating Point Arithmetic (FLP)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Floating Point Arithmetic (FLP) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-873 definition and examples

CWE-874: CERT C++ Secure Coding Section 06 - Arrays and the STL (ARR)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Arrays and the STL (ARR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-874 definition and examples

CWE-875: CERT C++ Secure Coding Section 07 - Characters and Strings (STR)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Characters and Strings (STR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-875 definition and examples

CWE-876: CERT C++ Secure Coding Section 08 - Memory Management (MEM)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Memory Management (MEM) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-876 definition and examples

CWE-877: CERT C++ Secure Coding Section 09 - Input Output (FIO)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Input Output (FIO) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-877 definition and examples

CWE-878: CERT C++ Secure Coding Section 10 - Environment (ENV)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Environment (ENV) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-878 definition and examples

CWE-879: CERT C++ Secure Coding Section 11 - Signals (SIG)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Signals (SIG) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-879 definition and examples

CWE-880: CERT C++ Secure Coding Section 12 - Exceptions and Error Handling (ERR)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Exceptions and Error Handling (ERR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-880 definition and examples

CWE-881: CERT C++ Secure Coding Section 13 - Object Oriented Programming (OOP)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Object Oriented Programming (OOP) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-881 definition and examples

CWE-882: CERT C++ Secure Coding Section 14 - Concurrency (CON)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Concurrency (CON) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-882 definition and examples

CWE-883: CERT C++ Secure Coding Section 49 - Miscellaneous (MSC)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to rules in the Miscellaneous (MSC) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.

More about CWE-883 definition and examples

CWE-885: SFP Primary Cluster: Risky Values

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Risky Values cluster (SFP1).

More about CWE-885 definition and examples

CWE-886: SFP Primary Cluster: Unused entities

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Unused entities cluster (SFP2).

More about CWE-886 definition and examples

CWE-887: SFP Primary Cluster: API

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the API cluster (SFP3).

More about CWE-887 definition and examples

CWE-889: SFP Primary Cluster: Exception Management

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Exception Management cluster (SFP4, SFP5, SFP6).

More about CWE-889 definition and examples

CWE-890: SFP Primary Cluster: Memory Access

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Memory Access cluster (SFP7, SFP8).

More about CWE-890 definition and examples

CWE-891: SFP Primary Cluster: Memory Management

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Memory Management cluster (SFP38).

More about CWE-891 definition and examples

CWE-892: SFP Primary Cluster: Resource Management

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Resource Management cluster (SFP37).

More about CWE-892 definition and examples

CWE-893: SFP Primary Cluster: Path Resolution

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Path Resolution cluster (SFP16, SFP17, SFP18).

More about CWE-893 definition and examples

CWE-894: SFP Primary Cluster: Synchronization

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Synchronization cluster (SFP19, SFP20, SFP21, SFP22).

More about CWE-894 definition and examples

CWE-895: SFP Primary Cluster: Information Leak

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Information Leak cluster (SFP23).

More about CWE-895 definition and examples

CWE-896: SFP Primary Cluster: Tainted Input

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Tainted Input cluster (SFP24, SFP25, SFP26, SFP27).

More about CWE-896 definition and examples

CWE-897: SFP Primary Cluster: Entry Points

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Entry Points cluster (SFP28).

More about CWE-897 definition and examples

CWE-898: SFP Primary Cluster: Authentication

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Authentication cluster (SFP29, SFP30, SFP31, SFP32, SFP33, SFP34).

More about CWE-898 definition and examples

CWE-899: SFP Primary Cluster: Access Control

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Access Control cluster (SFP35).

More about CWE-899 definition and examples

CWE-901: SFP Primary Cluster: Privilege

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Privilege cluster (SFP36).

More about CWE-901 definition and examples

CWE-902: SFP Primary Cluster: Channel

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Channel cluster.

More about CWE-902 definition and examples

CWE-903: SFP Primary Cluster: Cryptography

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Cryptography cluster.

More about CWE-903 definition and examples

CWE-904: SFP Primary Cluster: Malware

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Malware cluster.

More about CWE-904 definition and examples

CWE-905: SFP Primary Cluster: Predictability

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Predictability cluster.

More about CWE-905 definition and examples

CWE-906: SFP Primary Cluster: UI

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the UI cluster.

More about CWE-906 definition and examples

CWE-907: SFP Primary Cluster: Other

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Other cluster.

More about CWE-907 definition and examples

CWE-908: Use of Uninitialized Resource

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses or accesses a resource that has not been initialized.

More about CWE-908 definition and examples

Related CWE

CWE-909: Missing Initialization of Resource

  • Status: Incomplete
  • Weakness Abstractions: Base

The software does not initialize a critical resource.

More about CWE-909 definition and examples

Related CWE

CWE-910: Use of Expired File Descriptor

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses or accesses a file descriptor after it has been closed.

More about CWE-910 definition and examples

Related CWE

CWE-911: Improper Update of Reference Count

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.

More about CWE-911 definition and examples

Related CWE

CWE-912: Hidden Functionality

  • Status: Incomplete
  • Weakness Abstractions: Class

The software contains functionality that is not documented, not part of the specification, and not accessible through an interface or command sequence that is obvious to the software’s users or administrators.

More about CWE-912 definition and examples

Related CWE

CWE-913: Improper Control of Dynamically-Managed Code Resources

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.

More about CWE-913 definition and examples

Related CWE

CWE-914: Improper Control of Dynamically-Identified Variables

  • Status: Incomplete
  • Weakness Abstractions: Base

The software does not properly restrict reading from or writing to dynamically-identified variables.

More about CWE-914 definition and examples

Related CWE

CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes

  • Status: Incomplete
  • Weakness Abstractions: Base

The software receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.

More about CWE-915 definition and examples

Related CWE

CWE-916: Use of Password Hash With Insufficient Computational Effort

  • Status: Incomplete
  • Weakness Abstractions: Base

The software generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive.

More about CWE-916 definition and examples

Related CWE

CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement (‘Expression Language Injection’)

  • Status: Incomplete
  • Weakness Abstractions: Base

The software constructs all or part of an expression language (EL) statement in a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.

More about CWE-917 definition and examples

Related CWE

CWE-918: Server-Side Request Forgery (SSRF)

  • Status: Incomplete
  • Weakness Abstractions: Base

This entry has been deprecated. It originally came from PLOVER, which sometimes defined “other” and “miscellaneous” categories in order to satisfy exhaustiveness requirements for taxonomies. Within the context of CWE, the use of a more abstract entry is preferred in mapping situations. CWE-75 is a more appropriate mapping.

More about CWE-918 definition and examples

Related CWE

CWE-920: Improper Restriction of Power Consumption

  • Status: Incomplete
  • Weakness Abstractions: Base

The software operates in an environment in which power is a limited resource that cannot be automatically replenished, but the software does not properly restrict the amount of power that its operation consumes.

More about CWE-920 definition and examples

Related CWE

CWE-921: Storage of Sensitive Data in a Mechanism without Access Control

  • Status: Incomplete
  • Weakness Abstractions: Base

The software stores sensitive information in a file system or device that does not have built-in access control.

More about CWE-921 definition and examples

Related CWE

CWE-922: Insecure Storage of Sensitive Information

  • Status: Incomplete
  • Weakness Abstractions: Class

The software stores sensitive information without properly limiting read or write access by unauthorized actors.

More about CWE-922 definition and examples

Related CWE

CWE-923: Improper Restriction of Communication Channel to Intended Endpoints

  • Status: Incomplete
  • Weakness Abstractions: Class

The software establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.

More about CWE-923 definition and examples

Related CWE

CWE-924: Improper Enforcement of Message Integrity During Transmission in a Communication Channel

  • Status: Incomplete
  • Weakness Abstractions: Base

The software establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission.

More about CWE-924 definition and examples

Related CWE

CWE-925: Improper Verification of Intent by Broadcast Receiver

  • Status: Incomplete
  • Weakness Abstractions: Variant

The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.

More about CWE-925 definition and examples

Related CWE

CWE-926: Improper Export of Android Application Components

  • Status: Incomplete
  • Weakness Abstractions: Variant

The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.

More about CWE-926 definition and examples

Related CWE

CWE-927: Use of Implicit Intent for Sensitive Communication

  • Status: Incomplete
  • Weakness Abstractions: Variant

The Android application uses an implicit intent for transmitting sensitive data to other applications.

More about CWE-927 definition and examples

Related CWE

CWE-929: OWASP Top Ten 2013 Category A1 - Injection

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2013.

More about CWE-929 definition and examples

CWE-930: OWASP Top Ten 2013 Category A2 - Broken Authentication and Session Management

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2013.

More about CWE-930 definition and examples

CWE-931: OWASP Top Ten 2013 Category A3 - Cross-Site Scripting (XSS)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2013.

More about CWE-931 definition and examples

CWE-932: OWASP Top Ten 2013 Category A4 - Insecure Direct Object References

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2013.

More about CWE-932 definition and examples

CWE-933: OWASP Top Ten 2013 Category A5 - Security Misconfiguration

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2013.

More about CWE-933 definition and examples

CWE-934: OWASP Top Ten 2013 Category A6 - Sensitive Data Exposure

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2013.

More about CWE-934 definition and examples

CWE-935: OWASP Top Ten 2013 Category A7 - Missing Function Level Access Control

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2013.

More about CWE-935 definition and examples

CWE-936: OWASP Top Ten 2013 Category A8 - Cross-Site Request Forgery (CSRF)

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2013.

More about CWE-936 definition and examples

CWE-937: OWASP Top Ten 2013 Category A9 - Using Components with Known Vulnerabilities

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2013.

More about CWE-937 definition and examples

CWE-938: OWASP Top Ten 2013 Category A10 - Unvalidated Redirects and Forwards

  • Status: Obsolete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2013.

More about CWE-938 definition and examples

CWE-939: Improper Authorization in Handler for Custom URL Scheme

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a handler for a custom URL scheme, but it does not properly restrict which actors can invoke the handler using the scheme.

More about CWE-939 definition and examples

Related CWE

CWE-940: Improper Verification of Source of a Communication Channel

  • Status: Incomplete
  • Weakness Abstractions: Base

The software establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.

More about CWE-940 definition and examples

Related CWE

CWE-941: Incorrectly Specified Destination in a Communication Channel

  • Status: Incomplete
  • Weakness Abstractions: Base

The software creates a communication channel to initiate an outgoing request to an actor, but it does not correctly specify the intended destination for that actor.

More about CWE-941 definition and examples

Related CWE

CWE-942: Permissive Cross-domain Policy with Untrusted Domains

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software uses a cross-domain policy file that includes domains that should not be trusted.

More about CWE-942 definition and examples

Related CWE

CWE-943: Improper Neutralization of Special Elements in Data Query Logic

  • Status: Incomplete
  • Weakness Abstractions: Class

The application generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.

More about CWE-943 definition and examples

Related CWE

CWE-944: SFP Secondary Cluster: Access Management

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Access Management cluster.

More about CWE-944 definition and examples

CWE-945: SFP Secondary Cluster: Insecure Resource Access

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Insecure Resource Access cluster (SFP35).

More about CWE-945 definition and examples

CWE-946: SFP Secondary Cluster: Insecure Resource Permissions

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Insecure Resource Permissions cluster.

More about CWE-946 definition and examples

CWE-947: SFP Secondary Cluster: Authentication Bypass

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Authentication Bypass cluster.

More about CWE-947 definition and examples

CWE-948: SFP Secondary Cluster: Digital Certificate

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Digital Certificate cluster.

More about CWE-948 definition and examples

CWE-949: SFP Secondary Cluster: Faulty Endpoint Authentication

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Faulty Endpoint Authentication cluster (SFP29).

More about CWE-949 definition and examples

CWE-950: SFP Secondary Cluster: Hardcoded Sensitive Data

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Hardcoded Sensitive Data cluster (SFP33).

More about CWE-950 definition and examples

CWE-951: SFP Secondary Cluster: Insecure Authentication Policy

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Insecure Authentication Policy cluster.

More about CWE-951 definition and examples

CWE-952: SFP Secondary Cluster: Missing Authentication

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Missing Authentication cluster.

More about CWE-952 definition and examples

CWE-953: SFP Secondary Cluster: Missing Endpoint Authentication

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Missing Endpoint Authentication cluster (SFP30).

More about CWE-953 definition and examples

CWE-954: SFP Secondary Cluster: Multiple Binds to the Same Port

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Multiple Binds to the Same Port cluster (SFP32).

More about CWE-954 definition and examples

CWE-955: SFP Secondary Cluster: Unrestricted Authentication

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Unrestricted Authentication cluster (SFP34).

More about CWE-955 definition and examples

CWE-956: SFP Secondary Cluster: Channel Attack

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Channel Attack cluster.

More about CWE-956 definition and examples

CWE-957: SFP Secondary Cluster: Protocol Error

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Protocol Error cluster.

More about CWE-957 definition and examples

CWE-958: SFP Secondary Cluster: Broken Cryptography

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Broken Cryptography cluster.

More about CWE-958 definition and examples

CWE-959: SFP Secondary Cluster: Weak Cryptography

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Weak Cryptography cluster.

More about CWE-959 definition and examples

CWE-960: SFP Secondary Cluster: Ambiguous Exception Type

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Ambiguous Exception Type cluster (SFP5).

More about CWE-960 definition and examples

CWE-961: SFP Secondary Cluster: Incorrect Exception Behavior

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Incorrect Exception Behavior cluster (SFP6).

More about CWE-961 definition and examples

CWE-962: SFP Secondary Cluster: Unchecked Status Condition

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Unchecked Status Condition cluster (SFP4).

More about CWE-962 definition and examples

CWE-963: SFP Secondary Cluster: Exposed Data

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Exposed Data cluster (SFP23).

More about CWE-963 definition and examples

CWE-964: SFP Secondary Cluster: Exposure Temporary File

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Exposure Temporary File cluster.

More about CWE-964 definition and examples

CWE-965: SFP Secondary Cluster: Insecure Session Management

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Insecure Session Management cluster.

More about CWE-965 definition and examples

CWE-966: SFP Secondary Cluster: Other Exposures

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Other Exposures cluster.

More about CWE-966 definition and examples

CWE-967: SFP Secondary Cluster: State Disclosure

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the State Disclosure cluster.

More about CWE-967 definition and examples

CWE-968: SFP Secondary Cluster: Covert Channel

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Covert Channel cluster.

More about CWE-968 definition and examples

CWE-969: SFP Secondary Cluster: Faulty Memory Release

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Faulty Memory Release cluster (SFP12).

More about CWE-969 definition and examples

CWE-970: SFP Secondary Cluster: Faulty Buffer Access

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Faulty Buffer Access cluster (SFP8).

More about CWE-970 definition and examples

CWE-971: SFP Secondary Cluster: Faulty Pointer Use

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Faulty Pointer Use cluster (SFP7).

More about CWE-971 definition and examples

CWE-972: SFP Secondary Cluster: Faulty String Expansion

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Faulty String Expansion cluster (SFP9).

More about CWE-972 definition and examples

CWE-973: SFP Secondary Cluster: Improper NULL Termination

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Improper NULL Termination cluster (SFP11).

More about CWE-973 definition and examples

CWE-974: SFP Secondary Cluster: Incorrect Buffer Length Computation

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Incorrect Buffer Length Computation cluster (SFP10).

More about CWE-974 definition and examples

CWE-975: SFP Secondary Cluster: Architecture

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Architecture cluster.

More about CWE-975 definition and examples

CWE-976: SFP Secondary Cluster: Compiler

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Compiler cluster.

More about CWE-976 definition and examples

CWE-977: SFP Secondary Cluster: Design

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Design cluster.

More about CWE-977 definition and examples

CWE-978: SFP Secondary Cluster: Implementation

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Implementation cluster.

More about CWE-978 definition and examples

CWE-979: SFP Secondary Cluster: Failed Chroot Jail

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Failed Chroot Jail cluster (SFP17).

More about CWE-979 definition and examples

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Link in Resource Name Resolution cluster (SFP18).

More about CWE-980 definition and examples

CWE-981: SFP Secondary Cluster: Path Traversal

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Path Traversal cluster (SFP16).

More about CWE-981 definition and examples

CWE-982: SFP Secondary Cluster: Failure to Release Resource

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Failure to Release Resource cluster (SFP14).

More about CWE-982 definition and examples

CWE-983: SFP Secondary Cluster: Faulty Resource Use

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Faulty Resource Use cluster (SFP15).

More about CWE-983 definition and examples

CWE-984: SFP Secondary Cluster: Life Cycle

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Life Cycle cluster.

More about CWE-984 definition and examples

CWE-985: SFP Secondary Cluster: Unrestricted Consumption

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Unrestricted Consumption cluster (SFP13).

More about CWE-985 definition and examples

CWE-986: SFP Secondary Cluster: Missing Lock

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Missing Lock cluster (SFP19).

More about CWE-986 definition and examples

CWE-987: SFP Secondary Cluster: Multiple Locks/Unlocks

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Multiple Locks/Unlocks cluster (SFP21).

More about CWE-987 definition and examples

CWE-988: SFP Secondary Cluster: Race Condition Window

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Race Condition Window cluster (SFP20).

More about CWE-988 definition and examples

CWE-989: SFP Secondary Cluster: Unrestricted Lock

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Unrestricted Lock cluster (SFP22).

More about CWE-989 definition and examples

CWE-990: SFP Secondary Cluster: Tainted Input to Command

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Command cluster (SFP24).

More about CWE-990 definition and examples

CWE-991: SFP Secondary Cluster: Tainted Input to Environment

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Environment cluster (SFP27).

More about CWE-991 definition and examples

CWE-992: SFP Secondary Cluster: Faulty Input Transformation

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Faulty Input Transformation cluster.

More about CWE-992 definition and examples

CWE-993: SFP Secondary Cluster: Incorrect Input Handling

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Incorrect Input Handling cluster.

More about CWE-993 definition and examples

CWE-994: SFP Secondary Cluster: Tainted Input to Variable

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Variable cluster (SFP25).

More about CWE-994 definition and examples

CWE-995: SFP Secondary Cluster: Feature

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Feature cluster.

More about CWE-995 definition and examples

CWE-996: SFP Secondary Cluster: Security

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Security cluster.

More about CWE-996 definition and examples

CWE-997: SFP Secondary Cluster: Information Loss

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Information Loss cluster.

More about CWE-997 definition and examples

CWE-998: SFP Secondary Cluster: Glitch in Computation

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Glitch in Computation cluster (SFP1).

More about CWE-998 definition and examples

CWE-1001: SFP Secondary Cluster: Use of an Improper API

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Use of an Improper API cluster (SFP3).

More about CWE-1001 definition and examples

CWE-1002: SFP Secondary Cluster: Unexpected Entry Points

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Unexpected Entry Points cluster.

More about CWE-1002 definition and examples

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.

More about CWE-1004 definition and examples

Related CWE

CWE-1005: 7PK - Input Validation and Representation

  • Status: Draft
  • Weakness Abstractions: Category

This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that exist when an application does not properly validate or represent input. According to the authors of the Seven Pernicious Kingdoms, “Input validation and representation problems are caused by metacharacters, alternate encodings and numeric representations. Security problems result from trusting input.”

More about CWE-1005 definition and examples

CWE-1006: Bad Coding Practices

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to coding practices that are deemed unsafe and increase the chances that an exploitable vulnerability will be present in the application. These weaknesses do not directly introduce a vulnerability, but indicate that the product has not been carefully developed or maintained. If a program is complex, difficult to maintain, not portable, or shows evidence of neglect, then there is a higher likelihood that weaknesses are buried in the code.

More about CWE-1006 definition and examples

CWE-1007: Insufficient Visual Distinction of Homoglyphs Presented to User

  • Status: Incomplete
  • Weakness Abstractions: Base

The software displays information or identifiers to a user, but the display mechanism does not make it easy for the user to distinguish between visually similar or identical glyphs (homoglyphs), which may cause the user to misinterpret a glyph and perform an unintended, insecure action.

More about CWE-1007 definition and examples

Related CWE

CWE-1009: Audit

  • Status: Draft
  • Weakness Abstractions: Category

This category has been deprecated. It was originally used for organizing the Development View (CWE-69 9), but it introduced unnecessary complexity and depth to the resulting tree.

More about CWE-1009 definition and examples

CWE-1010: Authenticate Actors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of authentication components of the system. Frequently these deal with verifying the entity is indeed who it claims to be. The weaknesses in this category could lead to a degradation of the quality of authentication if they are not addressed when designing or implementing a secure architecture.

More about CWE-1010 definition and examples

CWE-1011: Authorize Actors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of a system’s authorization components. Frequently these deal with enforcing that agents have the required permissions before performing certain operations, such as modifying data. The weaknesses in this category could lead to a degradation of quality of the authorization capability if they are not addressed when designing or implementing a secure architecture.

More about CWE-1011 definition and examples

CWE-1012: Cross Cutting

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of multiple security tactics and how they affect a system. For example, information exposure can impact the Limit Access and Limit Exposure security tactics. The weaknesses in this category could lead to a degradation of the quality of many capabilities if they are not addressed when designing or implementing a secure architecture.

More about CWE-1012 definition and examples

CWE-1013: Encrypt Data

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of data confidentiality in a system. Frequently these deal with the use of encryption libraries. The weaknesses in this category could lead to a degradation of the quality data encryption if they are not addressed when designing or implementing a secure architecture.

More about CWE-1013 definition and examples

CWE-1014: Identify Actors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of a system’s identification management components. Frequently these deal with verifying that external agents provide inputs into the system. The weaknesses in this category could lead to a degradation of the quality of identification management if they are not addressed when designing or implementing a secure architecture.

More about CWE-1014 definition and examples

CWE-1015: Limit Access

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of system resources. Frequently these deal with restricting the amount of resources that are accessed by actors, such as memory, network connections, CPU or access points. The weaknesses in this category could lead to a degradation of the quality of authentication if they are not addressed when designing or implementing a secure architecture.

More about CWE-1015 definition and examples

CWE-1016: Limit Exposure

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of the entry points to a system. Frequently these deal with minimizing the attack surface through designing the system with the least needed amount of entry points. The weaknesses in this category could lead to a degradation of a system’s defenses if they are not addressed when designing or implementing a secure architecture.

More about CWE-1016 definition and examples

CWE-1017: Lock Computer

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of a system’s lockout mechanism. Frequently these deal with scenarios that take effect in case of multiple failed attempts to access a given resource. The weaknesses in this category could lead to a degradation of access to system assets if they are not addressed when designing or implementing a secure architecture.

More about CWE-1017 definition and examples

CWE-1018: Manage User Sessions

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of session management. Frequently these deal with the information or status about each user and their access rights for the duration of multiple requests. The weaknesses in this category could lead to a degradation of the quality of session management if they are not addressed when designing or implementing a secure architecture.

More about CWE-1018 definition and examples

CWE-1019: Validate Inputs

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of a system’s input validation components. Frequently these deal with sanitizing, neutralizing and validating any externally provided inputs to minimize malformed data from entering the system and preventing code injection in the input data. The weaknesses in this category could lead to a degradation of the quality of data flow in a system if they are not addressed when designing or implementing a secure architecture.

More about CWE-1019 definition and examples

CWE-1020: Verify Message Integrity

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the design and architecture of a system’s data integrity components. Frequently these deal with ensuring integrity of data, such as messages, resource files, deployment files, and configuration files. The weaknesses in this category could lead to a degradation of data integrity quality if they are not addressed when designing or implementing a secure architecture.

More about CWE-1020 definition and examples

CWE-1021: Improper Restriction of Rendered UI Layers or Frames

  • Status: Incomplete
  • Weakness Abstractions: Base

The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with.

More about CWE-1021 definition and examples

Related CWE

  • Status: Incomplete
  • Weakness Abstractions: Variant

The web application produces links to untrusted external sites outside of its sphere of control, but it does not properly prevent the external site from modifying security-critical properties of the window.opener object, such as the location property.

More about CWE-1022 definition and examples

Related CWE

CWE-1023: Incomplete Comparison with Missing Factors

  • Status: Incomplete
  • Weakness Abstractions: Class

The software performs a comparison between entities that must consider multiple factors or characteristics of each entity, but the comparison does not include one or more of these factors.

More about CWE-1023 definition and examples

Related CWE

CWE-1024: Comparison of Incompatible Types

  • Status: Incomplete
  • Weakness Abstractions: Base

The software performs a comparison between two entities, but the entities are of different, incompatible types that cannot be guaranteed to provide correct results when they are directly compared.

More about CWE-1024 definition and examples

Related CWE

CWE-1025: Comparison Using Wrong Factors

  • Status: Incomplete
  • Weakness Abstractions: Base

The code performs a comparison between two entities, but the comparison examines the wrong factors or characteristics of the entities, which can lead to incorrect results and resultant weaknesses.

More about CWE-1025 definition and examples

Related CWE

CWE-1027: OWASP Top Ten 2017 Category A1 - Injection

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2017.

More about CWE-1027 definition and examples

CWE-1028: OWASP Top Ten 2017 Category A2 - Broken Authentication

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2017.

More about CWE-1028 definition and examples

CWE-1029: OWASP Top Ten 2017 Category A3 - Sensitive Data Exposure

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2017.

More about CWE-1029 definition and examples

CWE-1030: OWASP Top Ten 2017 Category A4 - XML External Entities (XXE)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2017.

More about CWE-1030 definition and examples

CWE-1031: OWASP Top Ten 2017 Category A5 - Broken Access Control

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2017.

More about CWE-1031 definition and examples

CWE-1032: OWASP Top Ten 2017 Category A6 - Security Misconfiguration

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2017.

More about CWE-1032 definition and examples

CWE-1033: OWASP Top Ten 2017 Category A7 - Cross-Site Scripting (XSS)

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2017.

More about CWE-1033 definition and examples

CWE-1034: OWASP Top Ten 2017 Category A8 - Insecure Deserialization

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2017.

More about CWE-1034 definition and examples

CWE-1035: OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2017.

More about CWE-1035 definition and examples

CWE-1036: OWASP Top Ten 2017 Category A10 - Insufficient Logging & Monitoring

  • Status: Incomplete
  • Weakness Abstractions: Category

Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2017.

More about CWE-1036 definition and examples

CWE-1037: Processor Optimization Removal or Modification of Security-critical Code

  • Status: Incomplete
  • Weakness Abstractions: Base

This weakness does not depend on other weaknesses and is the result of choices made by the processor in executing the specified application.

More about CWE-1037 definition and examples

Related CWE

CWE-1038: Insecure Automated Optimizations

  • Status: Draft
  • Weakness Abstractions: Class

This weakness does not depend on other weaknesses and is the result of choices made during optimization.

More about CWE-1038 definition and examples

Related CWE

CWE-1039: Automated Recognition Mechanism with Inadequate Detection or Handling of Adversarial Input Perturbations

  • Status: Incomplete
  • Weakness Abstractions: Class

This weakness does not depend on other weaknesses and is the result of choices made during optimization.

More about CWE-1039 definition and examples

Related CWE

CWE-1041: Use of Redundant Code

  • Status: Incomplete
  • Weakness Abstractions: Base

The software has multiple functions, methods, procedures, macros, etc. that contain the same code.

More about CWE-1041 definition and examples

Related CWE

CWE-1042: Static Member Data Element outside of a Singleton Class Element

  • Status: Incomplete
  • Weakness Abstractions: Variant

The code contains a member element that is declared as static (but not final), in which its parent class element is not a singleton class - that is, a class element that can be used only once in the ’to’ association of a Create action.

More about CWE-1042 definition and examples

Related CWE

CWE-1043: Data Element Aggregating an Excessively Large Number of Non-Primitive Elements

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a data element that has an excessively large number of sub-elements with non-primitive data types such as structures or aggregated objects.

More about CWE-1043 definition and examples

Related CWE

CWE-1044: Architecture with Number of Horizontal Layers Outside of Expected Range

  • Status: Incomplete
  • Weakness Abstractions: Base

The software’s architecture contains too many - or too few - horizontal layers.

More about CWE-1044 definition and examples

Related CWE

CWE-1045: Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor

  • Status: Incomplete
  • Weakness Abstractions: Variant

A parent class has a virtual destructor method, but the parent has a child class that does not have a virtual destructor.

More about CWE-1045 definition and examples

Related CWE

CWE-1046: Creation of Immutable Text Using String Concatenation

  • Status: Incomplete
  • Weakness Abstractions: Base

The software creates an immutable text string using string concatenation operations.

More about CWE-1046 definition and examples

Related CWE

CWE-1047: Modules with Circular Dependencies

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains modules in which one module has references that cycle back to itself, i.e., there are circular dependencies.

More about CWE-1047 definition and examples

Related CWE

CWE-1048: Invokable Control Element with Large Number of Outward Calls

  • Status: Incomplete
  • Weakness Abstractions: Base

The code contains callable control elements that contain an excessively large number of references to other application objects external to the context of the callable, i.e. a Fan-Out value that is excessively large.

More about CWE-1048 definition and examples

Related CWE

CWE-1049: Excessive Data Query Operations in a Large Data Table

  • Status: Incomplete
  • Weakness Abstractions: Base

The software performs a data query with a large number of joins and sub-queries on a large data table.

More about CWE-1049 definition and examples

Related CWE

CWE-1050: Excessive Platform Resource Consumption within a Loop

  • Status: Incomplete
  • Weakness Abstractions: Base

The software has a loop body or loop condition that contains a control element that directly or indirectly consumes platform resources, e.g. messaging, sessions, locks, or file descriptors.

More about CWE-1050 definition and examples

Related CWE

CWE-1051: Initialization with Hard-Coded Network Resource Configuration Data

  • Status: Incomplete
  • Weakness Abstractions: Base

The software initializes data using hard-coded values that act as network resource identifiers.

More about CWE-1051 definition and examples

Related CWE

CWE-1052: Excessive Use of Hard-Coded Literals in Initialization

  • Status: Incomplete
  • Weakness Abstractions: Base

The software initializes a data element using a hard-coded literal that is not a simple integer or static constant element.

More about CWE-1052 definition and examples

Related CWE

CWE-1053: Missing Documentation for Design

  • Status: Incomplete
  • Weakness Abstractions: Base

The product does not have documentation that represents how it is designed.

More about CWE-1053 definition and examples

Related CWE

CWE-1054: Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer

  • Status: Incomplete
  • Weakness Abstractions: Base

The code at one architectural layer invokes code that resides at a deeper layer than the adjacent layer, i.e., the invocation skips at least one layer, and the invoked code is not part of a vertical utility layer that can be referenced from any horizontal layer.

More about CWE-1054 definition and examples

Related CWE

CWE-1055: Multiple Inheritance from Concrete Classes

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains a class with inheritance from more than one concrete class.

More about CWE-1055 definition and examples

Related CWE

CWE-1056: Invokable Control Element with Variadic Parameters

  • Status: Incomplete
  • Weakness Abstractions: Base

A named-callable or method control element has a signature that supports a variable (variadic) number of parameters or arguments.

More about CWE-1056 definition and examples

Related CWE

CWE-1057: Data Access Operations Outside of Expected Data Manager Component

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a dedicated, central data manager component as required by design, but it contains code that performs data-access operations that do not use this data manager.

More about CWE-1057 definition and examples

Related CWE

CWE-1058: Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element

  • Status: Incomplete
  • Weakness Abstractions: Base

The code contains a function or method that operates in a multi-threaded environment but owns an unsafe non-final static storable or member data element.

More about CWE-1058 definition and examples

Related CWE

CWE-1059: Incomplete Documentation

  • Status: Incomplete
  • Weakness Abstractions: Class

The documentation, whether on paper or in electronic form, does not contain descriptions of all the relevant elements of the product, such as its usage, structure, interfaces, design, implementation, configuration, operation, etc.

More about CWE-1059 definition and examples

Related CWE

CWE-1060: Excessive Number of Inefficient Server-Side Data Accesses

  • Status: Incomplete
  • Weakness Abstractions: Base

The software performs too many data queries without using efficient data processing functionality such as stored procedures.

More about CWE-1060 definition and examples

Related CWE

CWE-1061: Insufficient Encapsulation

  • Status: Incomplete
  • Weakness Abstractions: Class

The software does not sufficiently hide the internal representation and implementation details of data or methods, which might allow external components or modules to modify data unexpectedly, invoke unexpected functionality, or introduce dependencies that the programmer did not intend.

More about CWE-1061 definition and examples

Related CWE

CWE-1062: Parent Class with References to Child Class

  • Status: Incomplete
  • Weakness Abstractions: Base

The code has a parent class that contains references to a child class, its methods, or its members.

More about CWE-1062 definition and examples

Related CWE

CWE-1063: Creation of Class Instance within a Static Code Block

  • Status: Incomplete
  • Weakness Abstractions: Base

A static code block creates an instance of a class.

More about CWE-1063 definition and examples

Related CWE

CWE-1064: Invokable Control Element with Signature Containing an Excessive Number of Parameters

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains a function, subroutine, or method whose signature has an unnecessarily large number of parameters/arguments.

More about CWE-1064 definition and examples

Related CWE

CWE-1065: Runtime Resource Management Control Element in a Component Built to Run on Application Servers

  • Status: Incomplete
  • Weakness Abstractions: Base

The application uses deployed components from application servers, but it also uses low-level functions/methods for management of resources, instead of the API provided by the application server.

More about CWE-1065 definition and examples

Related CWE

CWE-1066: Missing Serialization Control Element

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains a serializable data element that does not have an associated serialization method.

More about CWE-1066 definition and examples

Related CWE

CWE-1067: Excessive Execution of Sequential Searches of Data Resource

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains a data query against an SQL table or view that is configured in a way that does not utilize an index and may cause sequential searches to be performed.

More about CWE-1067 definition and examples

Related CWE

CWE-1068: Inconsistency Between Implementation and Documented Design

  • Status: Incomplete
  • Weakness Abstractions: Base

The implementation of the product is not consistent with the design as described within the relevant documentation.

More about CWE-1068 definition and examples

Related CWE

CWE-1069: Empty Exception Block

  • Status: Incomplete
  • Weakness Abstractions: Base

An invokable code block contains an exception handling block that does not contain any code, i.e. is empty.

More about CWE-1069 definition and examples

Related CWE

CWE-1070: Serializable Data Element Containing non-Serializable Item Elements

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains a serializable, storable data element such as a field or member, but the data element contains member elements that are not serializable.

More about CWE-1070 definition and examples

Related CWE

CWE-1071: Empty Code Block

  • Status: Incomplete
  • Weakness Abstractions: Base

The source code contains a block that does not contain any code, i.e., the block is empty.

More about CWE-1071 definition and examples

Related CWE

CWE-1072: Data Resource Access without Use of Connection Pooling

  • Status: Incomplete
  • Weakness Abstractions: Base

The software accesses a data resource through a database without using a connection pooling capability.

More about CWE-1072 definition and examples

Related CWE

CWE-1073: Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains a client with a function or method that contains a large number of data accesses/queries that are sent through a data manager, i.e., does not use efficient database capabilities.

More about CWE-1073 definition and examples

Related CWE

CWE-1074: Class with Excessively Deep Inheritance

  • Status: Incomplete
  • Weakness Abstractions: Base

A class has an inheritance level that is too high, i.e., it has a large number of parent classes.

More about CWE-1074 definition and examples

Related CWE

CWE-1075: Unconditional Control Flow Transfer outside of Switch Block

  • Status: Incomplete
  • Weakness Abstractions: Base

The software performs unconditional control transfer (such as a “goto”) in code outside of a branching structure such as a switch block.

More about CWE-1075 definition and examples

Related CWE

CWE-1076: Insufficient Adherence to Expected Conventions

  • Status: Incomplete
  • Weakness Abstractions: Class

The product’s architecture, source code, design, documentation, or other artifact does not follow required conventions.

More about CWE-1076 definition and examples

Related CWE

CWE-1077: Floating Point Comparison with Incorrect Operator

  • Status: Incomplete
  • Weakness Abstractions: Variant

The code performs a comparison such as an equality test between two float (floating point) values, but it uses comparison operators that do not account for the possibility of loss of precision.

More about CWE-1077 definition and examples

Related CWE

CWE-1078: Inappropriate Source Code Style or Formatting

  • Status: Incomplete
  • Weakness Abstractions: Class

The source code does not follow desired style or formatting for indentation, white space, comments, etc.

More about CWE-1078 definition and examples

Related CWE

CWE-1079: Parent Class without Virtual Destructor Method

  • Status: Incomplete
  • Weakness Abstractions: Base

A parent class contains one or more child classes, but the parent class does not have a virtual destructor method.

More about CWE-1079 definition and examples

Related CWE

CWE-1080: Source Code File with Excessive Number of Lines of Code

  • Status: Incomplete
  • Weakness Abstractions: Base

A source code file has too many lines of code.

More about CWE-1080 definition and examples

Related CWE

CWE-1082: Class Instance Self Destruction Control Element

  • Status: Incomplete
  • Weakness Abstractions: Base

The code contains a class instance that calls the method or function to delete or destroy itself.

More about CWE-1082 definition and examples

Related CWE

CWE-1083: Data Access from Outside Expected Data Manager Component

  • Status: Incomplete
  • Weakness Abstractions: Base

The software is intended to manage data access through a particular data manager component such as a relational or non-SQL database, but it contains code that performs data access operations without using that component.

More about CWE-1083 definition and examples

Related CWE

CWE-1084: Invokable Control Element with Excessive File or Data Access Operations

  • Status: Incomplete
  • Weakness Abstractions: Base

A function or method contains too many operations that utilize a data manager or file resource.

More about CWE-1084 definition and examples

Related CWE

CWE-1085: Invokable Control Element with Excessive Volume of Commented-out Code

  • Status: Incomplete
  • Weakness Abstractions: Base

A function, method, procedure, etc. contains an excessive amount of code that has been commented out within its body.

More about CWE-1085 definition and examples

Related CWE

CWE-1086: Class with Excessive Number of Child Classes

  • Status: Incomplete
  • Weakness Abstractions: Base

A class contains an unnecessarily large number of children.

More about CWE-1086 definition and examples

Related CWE

CWE-1087: Class with Virtual Method without a Virtual Destructor

  • Status: Incomplete
  • Weakness Abstractions: Base

A class contains a virtual method, but the method does not have an associated virtual destructor.

More about CWE-1087 definition and examples

Related CWE

CWE-1088: Synchronous Access of Remote Resource without Timeout

  • Status: Incomplete
  • Weakness Abstractions: Base

The code has a synchronous call to a remote resource, but there is no timeout for the call, or the timeout is set to infinite.

More about CWE-1088 definition and examples

Related CWE

CWE-1089: Large Data Table with Excessive Number of Indices

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a large data table that contains an excessively large number of indices.

More about CWE-1089 definition and examples

Related CWE

CWE-1090: Method Containing Access of a Member Element from Another Class

  • Status: Incomplete
  • Weakness Abstractions: Base

A method for a class performs an operation that directly accesses a member element from another class.

More about CWE-1090 definition and examples

Related CWE

CWE-1091: Use of Object without Invoking Destructor Method

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains a method that accesses an object but does not later invoke the element’s associated finalize/destructor method.

More about CWE-1091 definition and examples

Related CWE

CWE-1092: Use of Same Invokable Control Element in Multiple Architectural Layers

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses the same control element across multiple architectural layers.

More about CWE-1092 definition and examples

Related CWE

CWE-1093: Excessively Complex Data Representation

  • Status: Incomplete
  • Weakness Abstractions: Class

The software uses an unnecessarily complex internal representation for its data structures or interrelationships between those structures.

More about CWE-1093 definition and examples

Related CWE

CWE-1094: Excessive Index Range Scan for a Data Resource

  • Status: Incomplete
  • Weakness Abstractions: Base

The software contains an index range scan for a large data table, but the scan can cover a large number of rows.

More about CWE-1094 definition and examples

Related CWE

CWE-1095: Loop Condition Value Update within the Loop

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a loop with a control flow condition based on a value that is updated within the body of the loop.

More about CWE-1095 definition and examples

Related CWE

CWE-1096: Singleton Class Instance Creation without Proper Locking or Synchronization

  • Status: Incomplete
  • Weakness Abstractions: Variant

The software implements a Singleton design pattern but does not use appropriate locking or other synchronization mechanism to ensure that the singleton class is only instantiated once.

More about CWE-1096 definition and examples

Related CWE

CWE-1097: Persistent Storable Data Element without Associated Comparison Control Element

  • Status: Incomplete
  • Weakness Abstractions: Base

The software uses a storable data element that does not have all of the associated functions or methods that are necessary to support comparison.

More about CWE-1097 definition and examples

Related CWE

CWE-1098: Data Element containing Pointer Item without Proper Copy Control Element

  • Status: Incomplete
  • Weakness Abstractions: Variant

The code contains a data element with a pointer that does not have an associated copy or constructor method.

More about CWE-1098 definition and examples

Related CWE

CWE-1099: Inconsistent Naming Conventions for Identifiers

  • Status: Incomplete
  • Weakness Abstractions: Base

The product’s code, documentation, or other artifacts do not consistently use the same naming conventions for variables, callables, groups of related callables, I/O capabilities, data types, file names, or similar types of elements.

More about CWE-1099 definition and examples

Related CWE

CWE-1100: Insufficient Isolation of System-Dependent Functions

  • Status: Incomplete
  • Weakness Abstractions: Base

The product or code does not isolate system-dependent functionality into separate standalone modules.

More about CWE-1100 definition and examples

Related CWE

CWE-1101: Reliance on Runtime Component in Generated Code

  • Status: Incomplete
  • Weakness Abstractions: Base

The product uses automatically-generated code that cannot be executed without a specific runtime support component.

More about CWE-1101 definition and examples

Related CWE

CWE-1102: Reliance on Machine-Dependent Data Representation

  • Status: Incomplete
  • Weakness Abstractions: Base

The code uses a data representation that relies on low-level data representation or constructs that may vary across different processors, physical machines, OSes, or other physical components.

More about CWE-1102 definition and examples

Related CWE

CWE-1103: Use of Platform-Dependent Third Party Components

  • Status: Incomplete
  • Weakness Abstractions: Base

The product relies on third-party software components that do not provide equivalent functionality across all desirable platforms.

More about CWE-1103 definition and examples

Related CWE

CWE-1104: Use of Unmaintained Third Party Components

  • Status: Incomplete
  • Weakness Abstractions: Base

The product relies on third-party components that are not actively supported or maintained by the original developer or a trusted proxy for the original developer.

More about CWE-1104 definition and examples

Related CWE

CWE-1105: Insufficient Encapsulation of Machine-Dependent Functionality

  • Status: Incomplete
  • Weakness Abstractions: Base

The product or code uses machine-dependent functionality, but it does not sufficiently encapsulate or isolate this functionality from the rest of the code.

More about CWE-1105 definition and examples

Related CWE

CWE-1106: Insufficient Use of Symbolic Constants

  • Status: Incomplete
  • Weakness Abstractions: Base

The source code uses literal constants that may need to change or evolve over time, instead of using symbolic constants.

More about CWE-1106 definition and examples

Related CWE

CWE-1107: Insufficient Isolation of Symbolic Constant Definitions

  • Status: Incomplete
  • Weakness Abstractions: Base

The source code uses symbolic constants, but it does not sufficiently place the definitions of these constants into a more centralized or isolated location.

More about CWE-1107 definition and examples

Related CWE

CWE-1108: Excessive Reliance on Global Variables

  • Status: Incomplete
  • Weakness Abstractions: Base

The code is structured in a way that relies too much on using or setting global variables throughout various points in the code, instead of preserving the associated information in a narrower, more local context.

More about CWE-1108 definition and examples

Related CWE

CWE-1109: Use of Same Variable for Multiple Purposes

  • Status: Incomplete
  • Weakness Abstractions: Base

The code contains a callable, block, or other code element in which the same variable is used to control more than one unique task or store more than one instance of data.

More about CWE-1109 definition and examples

Related CWE

CWE-1110: Incomplete Design Documentation

  • Status: Incomplete
  • Weakness Abstractions: Base

The product’s design documentation does not adequately describe control flow, data flow, system initialization, relationships between tasks, components, rationales, or other important aspects of the design.

More about CWE-1110 definition and examples

Related CWE

CWE-1111: Incomplete I/O Documentation

  • Status: Incomplete
  • Weakness Abstractions: Base

The product’s documentation does not adequately define inputs, outputs, or system/software interfaces.

More about CWE-1111 definition and examples

Related CWE

CWE-1112: Incomplete Documentation of Program Execution

  • Status: Incomplete
  • Weakness Abstractions: Base

The document does not fully define all mechanisms that are used to control or influence how product-specific programs are executed.

More about CWE-1112 definition and examples

Related CWE

CWE-1113: Inappropriate Comment Style

  • Status: Incomplete
  • Weakness Abstractions: Base

The source code uses comment styles or formats that are inconsistent or do not follow expected standards for the product.

More about CWE-1113 definition and examples

Related CWE

CWE-1114: Inappropriate Whitespace Style

  • Status: Incomplete
  • Weakness Abstractions: Base

The source code contains whitespace that is inconsistent across the code or does not follow expected standards for the product.

More about CWE-1114 definition and examples

Related CWE

CWE-1115: Source Code Element without Standard Prologue

  • Status: Incomplete
  • Weakness Abstractions: Base

The source code contains elements such as source files that do not consistently provide a prologue or header that has been standardized for the project.

More about CWE-1115 definition and examples

Related CWE

CWE-1116: Inaccurate Comments

  • Status: Incomplete
  • Weakness Abstractions: Base

The source code contains comments that do not accurately describe or explain aspects of the portion of the code with which the comment is associated.

More about CWE-1116 definition and examples

Related CWE

CWE-1117: Callable with Insufficient Behavioral Summary

  • Status: Incomplete
  • Weakness Abstractions: Base

The code contains a function or method whose signature and/or associated inline documentation does not sufficiently describe the callable’s inputs, outputs, side effects, assumptions, or return codes.

More about CWE-1117 definition and examples

Related CWE

CWE-1118: Insufficient Documentation of Error Handling Techniques

  • Status: Incomplete
  • Weakness Abstractions: Base

The documentation does not sufficiently describe the techniques that are used for error handling, exception processing, or similar mechanisms.

More about CWE-1118 definition and examples

Related CWE

CWE-1119: Excessive Use of Unconditional Branching

  • Status: Incomplete
  • Weakness Abstractions: Base

The code uses too many unconditional branches (such as “goto”).

More about CWE-1119 definition and examples

Related CWE

CWE-1120: Excessive Code Complexity

  • Status: Incomplete
  • Weakness Abstractions: Class

The code is too complex, as calculated using a well-defined, quantitative measure.

More about CWE-1120 definition and examples

Related CWE

CWE-1121: Excessive McCabe Cyclomatic Complexity

  • Status: Incomplete
  • Weakness Abstractions: Base

The code contains McCabe cyclomatic complexity that exceeds a desirable maximum.

More about CWE-1121 definition and examples

Related CWE

CWE-1122: Excessive Halstead Complexity

  • Status: Incomplete
  • Weakness Abstractions: Base

The code is structured in a way that a Halstead complexity measure exceeds a desirable maximum.

More about CWE-1122 definition and examples

Related CWE

CWE-1123: Excessive Use of Self-Modifying Code

  • Status: Incomplete
  • Weakness Abstractions: Base

The product uses too much self-modifying code.

More about CWE-1123 definition and examples

Related CWE

CWE-1124: Excessively Deep Nesting

  • Status: Incomplete
  • Weakness Abstractions: Base

The code contains a callable or other code grouping in which the nesting / branching is too deep.

More about CWE-1124 definition and examples

Related CWE

CWE-1125: Excessive Attack Surface

  • Status: Incomplete
  • Weakness Abstractions: Base

The product has an attack surface whose quantitative measurement exceeds a desirable maximum.

More about CWE-1125 definition and examples

Related CWE

CWE-1126: Declaration of Variable with Unnecessarily Wide Scope

  • Status: Incomplete
  • Weakness Abstractions: Base

The source code declares a variable in one scope, but the variable is only used within a narrower scope.

More about CWE-1126 definition and examples

Related CWE

CWE-1127: Compilation with Insufficient Warnings or Errors

  • Status: Incomplete
  • Weakness Abstractions: Base

The code is compiled without sufficient warnings enabled, which may prevent the detection of subtle bugs or quality issues.

More about CWE-1127 definition and examples

Related CWE

CWE-1129: CISQ Quality Measures (2016) - Reliability

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the CISQ Quality Measures for Reliability, as documented in 2016 with the Automated Source Code CISQ Reliability Measure (ASCRM) Specification 1.0. Presence of these weaknesses could reduce the reliability of the software.

More about CWE-1129 definition and examples

CWE-1130: CISQ Quality Measures (2016) - Maintainability

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the CISQ Quality Measures for Maintainability, as documented in 2016 with the Automated Source Code Maintainability Measure (ASCMM) Specification 1.0. Presence of these weaknesses could reduce the maintainability of the software.

More about CWE-1130 definition and examples

CWE-1131: CISQ Quality Measures (2016) - Security

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the CISQ Quality Measures for Security, as documented in 2016 with the Automated Source Code Security Measure (ASCSM) Specification 1.0. Presence of these weaknesses could reduce the security of the software.

More about CWE-1131 definition and examples

CWE-1132: CISQ Quality Measures (2016) - Performance Efficiency

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the CISQ Quality Measures for Performance Efficiency, as documented in 2016 with the Automated Source Code Performance Efficiency Measure (ASCPEM) Specification 1.0. Presence of these weaknesses could reduce the performance efficiency of the software.

More about CWE-1132 definition and examples

CWE-1134: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 00. Input Validation and Data Sanitization (IDS)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Input Validation and Data Sanitization (IDS) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1134 definition and examples

CWE-1135: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 01. Declarations and Initialization (DCL)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1135 definition and examples

CWE-1136: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 02. Expressions (EXP)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1136 definition and examples

CWE-1137: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 03. Numeric Types and Operations (NUM)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Numeric Types and Operations (NUM) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1137 definition and examples

CWE-1138: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 04. Characters and Strings (STR)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Characters and Strings (STR) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1138 definition and examples

CWE-1139: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 05. Object Orientation (OBJ)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Object Orientation (OBJ) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1139 definition and examples

CWE-1140: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 06. Methods (MET)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Methods (MET) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1140 definition and examples

CWE-1141: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 07. Exceptional Behavior (ERR)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Exceptional Behavior (ERR) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1141 definition and examples

CWE-1142: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 08. Visibility and Atomicity (VNA)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Visibility and Atomicity (VNA) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1142 definition and examples

CWE-1143: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 09. Locking (LCK)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Locking (LCK) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1143 definition and examples

CWE-1144: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 10. Thread APIs (THI)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Thread APIs (THI) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1144 definition and examples

CWE-1145: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 11. Thread Pools (TPS)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Thread Pools (TPS) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1145 definition and examples

CWE-1146: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 12. Thread-Safety Miscellaneous (TSM)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Thread-Safety Miscellaneous (TSM) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1146 definition and examples

CWE-1147: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 13. Input Output (FIO)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Input Output (FIO) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1147 definition and examples

CWE-1148: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 14. Serialization (SER)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Serialization (SER) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1148 definition and examples

CWE-1149: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 15. Platform Security (SEC)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Platform Security (SEC) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1149 definition and examples

CWE-1150: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 16. Runtime Environment (ENV)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Runtime Environment (ENV) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1150 definition and examples

CWE-1151: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 17. Java Native Interface (JNI)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Java Native Interface (JNI) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1151 definition and examples

CWE-1152: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 49. Miscellaneous (MSC)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1152 definition and examples

CWE-1153: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 50. Android (DRD)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Android (DRD) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1153 definition and examples

CWE-1155: SEI CERT C Coding Standard - Guidelines 01. Preprocessor (PRE)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Preprocessor (PRE) section of the SEI CERT C Coding Standard.

More about CWE-1155 definition and examples

CWE-1156: SEI CERT C Coding Standard - Guidelines 02. Declarations and Initialization (DCL)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) section of the SEI CERT C Coding Standard.

More about CWE-1156 definition and examples

CWE-1157: SEI CERT C Coding Standard - Guidelines 03. Expressions (EXP)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) section of the SEI CERT C Coding Standard.

More about CWE-1157 definition and examples

CWE-1158: SEI CERT C Coding Standard - Guidelines 04. Integers (INT)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Integers (INT) section of the SEI CERT C Coding Standard.

More about CWE-1158 definition and examples

CWE-1159: SEI CERT C Coding Standard - Guidelines 05. Floating Point (FLP)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Floating Point (FLP) section of the SEI CERT C Coding Standard.

More about CWE-1159 definition and examples

CWE-1160: SEI CERT C Coding Standard - Guidelines 06. Arrays (ARR)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Arrays (ARR) section of the SEI CERT C Coding Standard.

More about CWE-1160 definition and examples

CWE-1161: SEI CERT C Coding Standard - Guidelines 07. Characters and Strings (STR)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Characters and Strings (STR) section of the SEI CERT C Coding Standard.

More about CWE-1161 definition and examples

CWE-1162: SEI CERT C Coding Standard - Guidelines 08. Memory Management (MEM)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Memory Management (MEM) section of the SEI CERT C Coding Standard.

More about CWE-1162 definition and examples

CWE-1163: SEI CERT C Coding Standard - Guidelines 09. Input Output (FIO)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Input Output (FIO) section of the SEI CERT C Coding Standard.

More about CWE-1163 definition and examples

CWE-1164: Irrelevant Code

  • Status: Incomplete
  • Weakness Abstractions: Class

The program contains code that is not essential for execution, i.e. makes no state changes and has no side effects that alter data or control flow, such that removal of the code would have no impact to functionality or correctness.

More about CWE-1164 definition and examples

Related CWE

CWE-1165: SEI CERT C Coding Standard - Guidelines 10. Environment (ENV)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Environment (ENV) section of the SEI CERT C Coding Standard.

More about CWE-1165 definition and examples

CWE-1166: SEI CERT C Coding Standard - Guidelines 11. Signals (SIG)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Signals (SIG) section of the SEI CERT C Coding Standard.

More about CWE-1166 definition and examples

CWE-1167: SEI CERT C Coding Standard - Guidelines 12. Error Handling (ERR)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Error Handling (ERR) section of the SEI CERT C Coding Standard.

More about CWE-1167 definition and examples

CWE-1168: SEI CERT C Coding Standard - Guidelines 13. Application Programming Interfaces (API)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Application Programming Interfaces (API) section of the SEI CERT C Coding Standard.

More about CWE-1168 definition and examples

CWE-1169: SEI CERT C Coding Standard - Guidelines 14. Concurrency (CON)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Concurrency (CON) section of the SEI CERT C Coding Standard.

More about CWE-1169 definition and examples

CWE-1170: SEI CERT C Coding Standard - Guidelines 48. Miscellaneous (MSC)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) section of the SEI CERT C Coding Standard.

More about CWE-1170 definition and examples

CWE-1171: SEI CERT C Coding Standard - Guidelines 50. POSIX (POS)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the POSIX (POS) section of the SEI CERT C Coding Standard.

More about CWE-1171 definition and examples

CWE-1172: SEI CERT C Coding Standard - Guidelines 51. Microsoft Windows (WIN)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Microsoft Windows (WIN) section of the SEI CERT C Coding Standard.

More about CWE-1172 definition and examples

CWE-1173: Improper Use of Validation Framework

  • Status: Draft
  • Weakness Abstractions: Base

The application does not use, or incorrectly uses, an input validation framework that is provided by the source language or an independent library.

More about CWE-1173 definition and examples

Related CWE

CWE-1174: ASP.NET Misconfiguration: Improper Model Validation

  • Status: Draft
  • Weakness Abstractions: Variant

The ASP.NET application does not use, or incorrectly uses, the model validation framework.

More about CWE-1174 definition and examples

Related CWE

CWE-1175: SEI CERT Oracle Secure Coding Standard for Java - Guidelines 18. Concurrency (CON)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Concurrency (CON) section of the SEI CERT Oracle Secure Coding Standard for Java.

More about CWE-1175 definition and examples

CWE-1176: Inefficient CPU Computation

  • Status: Incomplete
  • Weakness Abstractions: Class

The program performs CPU computations using algorithms that are not as efficient as they could be for the needs of the developer, i.e., the computations can be optimized further.

More about CWE-1176 definition and examples

Related CWE

CWE-1177: Use of Prohibited Code

  • Status: Incomplete
  • Weakness Abstractions: Class

The software uses a function, library, or third party component that has been explicitly prohibited, whether by the developer or the customer.

More about CWE-1177 definition and examples

Related CWE

CWE-1179: SEI CERT Perl Coding Standard - Guidelines 01. Input Validation and Data Sanitization (IDS)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Input Validation and Data Sanitization (IDS) section of the SEI CERT Perl Coding Standard.

More about CWE-1179 definition and examples

CWE-1180: SEI CERT Perl Coding Standard - Guidelines 02. Declarations and Initialization (DCL)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) section of the SEI CERT Perl Coding Standard.

More about CWE-1180 definition and examples

CWE-1181: SEI CERT Perl Coding Standard - Guidelines 03. Expressions (EXP)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) section of the SEI CERT Perl Coding Standard.

More about CWE-1181 definition and examples

CWE-1182: SEI CERT Perl Coding Standard - Guidelines 04. Integers (INT)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Integers (INT) section of the SEI CERT Perl Coding Standard.

More about CWE-1182 definition and examples

CWE-1183: SEI CERT Perl Coding Standard - Guidelines 05. Strings (STR)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Strings (STR) section of the SEI CERT Perl Coding Standard.

More about CWE-1183 definition and examples

CWE-1184: SEI CERT Perl Coding Standard - Guidelines 06. Object-Oriented Programming (OOP)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Object-Oriented Programming (OOP) section of the SEI CERT Perl Coding Standard.

More about CWE-1184 definition and examples

CWE-1185: SEI CERT Perl Coding Standard - Guidelines 07. File Input and Output (FIO)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the File Input and Output (FIO) section of the SEI CERT Perl Coding Standard.

More about CWE-1185 definition and examples

CWE-1186: SEI CERT Perl Coding Standard - Guidelines 50. Miscellaneous (MSC)

  • Status: Stable
  • Weakness Abstractions: Category

Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) section of the SEI CERT Perl Coding Standard.

More about CWE-1186 definition and examples

CWE-1188: Insecure Default Initialization of Resource

  • Status: Incomplete
  • Weakness Abstractions: Base

The software initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.

More about CWE-1188 definition and examples

Related CWE

CWE-1189: Improper Isolation of Shared Resources on System-on-a-Chip (SoC)

  • Status: Draft
  • Weakness Abstractions: Base

The product does not properly isolate shared resources between trusted and untrusted agents.

More about CWE-1189 definition and examples

Related CWE

CWE-1190: DMA Device Enabled Too Early in Boot Phase

  • Status: Draft
  • Weakness Abstractions: Base

The product enables a Direct Memory Access (DMA) capable device before the security configuration settings are established, which allows an attacker to extract data from or gain privileges on the product.

More about CWE-1190 definition and examples

Related CWE

CWE-1191: Exposed Chip Debug and Test Interface With Insufficient or Missing Authorization

  • Status: Draft
  • Weakness Abstractions: Base

The chip does not implement or does not correctly check whether users are authorized to access internal registers.

More about CWE-1191 definition and examples

Related CWE

CWE-1192: System-on-Chip (SoC) Using Components without Unique, Immutable Identifiers

  • Status: Draft
  • Weakness Abstractions: Base

The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.

More about CWE-1192 definition and examples

Related CWE

CWE-1193: Power-On of Untrusted Execution Core Before Enabling Fabric Access Control

  • Status: Draft
  • Weakness Abstractions: Base

The product enables components that contain untrusted firmware before memory and fabric access controls have been enabled.

More about CWE-1193 definition and examples

Related CWE

CWE-1195: Manufacturing and Life Cycle Management Concerns

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are root-caused to defects that arise in the semiconductor-manufacturing process or during the life cycle and supply chain.

More about CWE-1195 definition and examples

CWE-1196: Security Flow Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to improper design of full-system security flows, including but not limited to secure boot, secure update, and hardware-device attestation.

More about CWE-1196 definition and examples

CWE-1197: Integration Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are those that arise due to integration of multiple hardware Intellectual Property (IP) cores, from System-on-a-Chip (SoC) subsystem interactions, or from hardware platform subsystem interactions.

More about CWE-1197 definition and examples

CWE-1198: Privilege Separation and Access Control Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to features and mechanisms providing hardware-based isolation and access control (e.g., identity, policy, locking control) of sensitive shared hardware resources such as registers and fuses.

More about CWE-1198 definition and examples

CWE-1199: General Circuit and Logic Design Concerns

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to hardware-circuit design and logic (e.g., CMOS transistors, finite state machines, and registers) as well as issues related to hardware description languages such as System Verilog and VHDL.

More about CWE-1199 definition and examples

CWE-1201: Core and Compute Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are typically associated with CPUs, Graphics, Vision, AI, FPGA, and microcontrollers.

More about CWE-1201 definition and examples

CWE-1202: Memory and Storage Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are typically associated with memory (e.g., DRAM, SRAM) and storage technologies (e.g., NAND Flash, OTP, EEPROM, and eMMC).

More about CWE-1202 definition and examples

CWE-1203: Peripherals, On-chip Fabric, and Interface/IO Problems

  • Status: Draft

  • Weakness Abstractions: Category

         Weaknesses in this category are related to hardware		   security problems that apply to peripheral devices, IO		   interfaces, on-chip interconnects, network-on-chip (NoC),		   and buses.  For example, this category includes issues		   related to design of hardware interconnect and/or protocols		   such as PCIe, USB, SMBUS, general-purpose IO pins, and		   user-input peripherals such as mouse and keyboard.		 
    

More about CWE-1203 definition and examples

CWE-1204: Generation of Weak Initialization Vector (IV)

  • Status: Incomplete
  • Weakness Abstractions: Base

The product uses a cryptographic primitive that uses an Initialization Vector (IV), but the product does not generate IVs that are sufficiently unpredictable or unique according to the expected cryptographic requirements for that primitive.

More about CWE-1204 definition and examples

Related CWE

CWE-1205: Security Primitives and Cryptography Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to hardware implementations of cryptographic protocols and other hardware-security primitives such as physical unclonable functions (PUFs) and random number generators (RNGs).

More about CWE-1205 definition and examples

CWE-1206: Power, Clock, and Reset Concerns

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to system power, voltage, current, temperature, clocks, system state saving/restoring, and resets at the platform and SoC level.

More about CWE-1206 definition and examples

CWE-1207: Debug and Test Problems

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to hardware debug and test interfaces such as JTAG and scan chain.

More about CWE-1207 definition and examples

CWE-1208: Cross-Cutting Problems

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category can arise in multiple areas of hardware design or can apply to a wide cross-section of components.

More about CWE-1208 definition and examples

CWE-1209: Failure to Disable Reserved Bits

  • Status: Incomplete
  • Weakness Abstractions: Base

The reserved bits in a hardware design are not disabled prior to production. Typically, reserved bits are used for future capabilities and should not support any functional logic in the design. However, designers might covertly use these bits to debug or further develop new capabilities in production hardware. Adversaries with access to these bits will write to them in hopes of compromising hardware state.

More about CWE-1209 definition and examples

Related CWE

CWE-1210: Audit / Logging Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to audit-based components of a software system. Frequently these deal with logging user activities in order to identify undesired access and modifications to the system. The weaknesses in this category could lead to a degradation of the quality of the audit capability if they are not addressed.

More about CWE-1210 definition and examples

CWE-1211: Authentication Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to authentication components of a system. Frequently these deal with the ability to verify that an entity is indeed who it claims to be. If not addressed when designing or implementing a software system, these weaknesses could lead to a degradation of the quality of the authentication capability.

More about CWE-1211 definition and examples

CWE-1212: Authorization Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to authorization components of a system. Frequently these deal with the ability to enforce that agents have the required permissions before performing certain operations, such as modifying data. If not addressed when designing or implementing a software system, these weaknesses could lead to a degradation of the quality of the authorization capability.

More about CWE-1212 definition and examples

CWE-1213: Random Number Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to a software system’s random number generation.

More about CWE-1213 definition and examples

CWE-1214: Data Integrity Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to a software system’s data integrity components. Frequently these deal with the ability to ensure the integrity of data, such as messages, resource files, deployment files, and configuration files. The weaknesses in this category could lead to a degradation of data integrity quality if they are not addressed.

More about CWE-1214 definition and examples

CWE-1215: Data Validation Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to a software system’s components for input validation, output validation, or other kinds of validation. Validation is a frequently-used technique for ensuring that data conforms to expectations before it is further processed as input or output. There are many varieties of validation (see CWE-20, which is just for input validation). Validation is distinct from other techniques that attempt to modify data before processing it, although developers may consider all attempts to product “safe” inputs or outputs as some kind of validation. Regardless, validation is a powerful tool that is often used to minimize malformed data from entering the system, or indirectly avoid code injection or other potentially-malicious patterns when generating output. The weaknesses in this category could lead to a degradation of the quality of data flow in a system if they are not addressed.

More about CWE-1215 definition and examples

CWE-1216: Lockout Mechanism Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to a software system’s lockout mechanism. Frequently these deal with scenarios that take effect in case of multiple failed attempts to access a given resource. The weaknesses in this category could lead to a degradation of access to system assets if they are not addressed.

More about CWE-1216 definition and examples

CWE-1217: User Session Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to session management. Frequently these deal with the information or status about each user and their access rights for the duration of multiple requests. The weaknesses in this category could lead to a degradation of the quality of session management if they are not addressed.

More about CWE-1217 definition and examples

CWE-1218: Memory Buffer Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the handling of memory buffers within a software system.

More about CWE-1218 definition and examples

CWE-1219: File Handling Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the handling of files within a software system. Files, directories, and folders are so central to information technology that many different weaknesses and variants have been discovered.

More about CWE-1219 definition and examples

CWE-1220: Insufficient Granularity of Access Control

  • Status: Incomplete
  • Weakness Abstractions: Base

The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.

More about CWE-1220 definition and examples

Related CWE

CWE-1221: Incorrect Register Defaults or Module Parameters

  • Status: Incomplete
  • Weakness Abstractions: Base

Hardware description language code incorrectly defines register defaults or hardware IP parameters to insecure values.

More about CWE-1221 definition and examples

Related CWE

CWE-1222: Insufficient Granularity of Address Regions Protected by Register Locks

  • Status: Incomplete
  • Weakness Abstractions: Variant

The product defines a large address region protected from modification by the same register lock control bit. This results in a conflict between the functional requirement that some addresses need to be writable by software during operation and the security requirement that the system configuration lock bit must be set during the boot process.

More about CWE-1222 definition and examples

Related CWE

CWE-1223: Race Condition for Write-Once Attributes

  • Status: Incomplete
  • Weakness Abstractions: Base

A write-once register in hardware design is programmable by an untrusted software component earlier than the trusted software component, resulting in a race condition issue.

More about CWE-1223 definition and examples

Related CWE

CWE-1224: Improper Restriction of Write-Once Bit Fields

  • Status: Incomplete
  • Weakness Abstractions: Base

The hardware design control register “sticky bits” or write-once bit fields are improperly implemented, such that they can be reprogrammed by software.

More about CWE-1224 definition and examples

Related CWE

CWE-1225: Documentation Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the documentation provide to support a product.

More about CWE-1225 definition and examples

CWE-1226: Complexity Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are associated with things being overly complex.

More about CWE-1226 definition and examples

CWE-1227: Encapsulation Issues

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to issues surrounding the bundling of data with the methods intended to operate on that data.

More about CWE-1227 definition and examples

CWE-1228: API / Function Errors

  • Status: Draft
  • Weakness Abstractions: Category

Weaknesses in this category are related to the use of built-in functions or external APIs.

More about CWE-1228 definition and examples

CWE-1229: Creation of Emergent Resource

  • Status: Incomplete
  • Weakness Abstractions: Class

The product manages resources or behaves in a way that indirectly creates a new, distinct resource that can be used by attackers in violation of the intended policy.

More about CWE-1229 definition and examples

Related CWE

CWE-1230: Exposure of Sensitive Information Through Metadata

  • Status: Incomplete
  • Weakness Abstractions: Base

The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information.

More about CWE-1230 definition and examples

Related CWE

CWE-1231: Improper Implementation of Lock Protection Registers

  • Status: Incomplete
  • Weakness Abstractions: Base

The product incorrectly implements register lock bit protection features such that protected controls can be programmed even after the lock has been set.

More about CWE-1231 definition and examples

Related CWE

CWE-1232: Improper Lock Behavior After Power State Transition

  • Status: Incomplete
  • Weakness Abstractions: Base

Register lock bit protection disables changes to system configuration once the bit is set. Some of the protected registers or lock bits become programmable after power state transitions (e.g., Entry and wake from low power sleep modes) causing the system configuration to be changeable.

More about CWE-1232 definition and examples

Related CWE

CWE-1233: Improper Hardware Lock Protection for Security Sensitive Controls

  • Status: Incomplete
  • Weakness Abstractions: Base

The product implements a register lock bit protection feature that permits security sensitive controls to modify the protected configuration.

More about CWE-1233 definition and examples

Related CWE

CWE-1234: Hardware Internal or Debug Modes Allow Override of Locks

  • Status: Incomplete
  • Weakness Abstractions: Base

System configuration protection may be bypassed during debug mode.

More about CWE-1234 definition and examples

Related CWE

CWE-1235: Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations

  • Status: Incomplete
  • Weakness Abstractions: Base

The code uses boxed primitives, which may introduce inefficiencies into performance-critical operations.

More about CWE-1235 definition and examples

Related CWE

CWE-1236: Improper Neutralization of Formula Elements in a CSV File

  • Status: Incomplete
  • Weakness Abstractions: Base

The software saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as a command when the file is opened by spreadsheet software.

More about CWE-1236 definition and examples

Related CWE

CWE-1237: SFP Primary Cluster: Faulty Resource Release

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Faulty Resource Release cluster (SFP37).

More about CWE-1237 definition and examples

CWE-1238: SFP Primary Cluster: Failure to Release Memory

  • Status: Incomplete
  • Weakness Abstractions: Category

This category identifies Software Fault Patterns (SFPs) within the Failure to Release Memory cluster (SFP38).

More about CWE-1238 definition and examples

CWE-1239: Improper Zeroization of Hardware Register

  • Status: Draft
  • Weakness Abstractions: Variant

The hardware product does not properly clear sensitive information from built-in registers when the user of the hardware block changes.

More about CWE-1239 definition and examples

Related CWE