Improper Neutralization

Opis

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.

If a message is malformed, it may cause the message to be incorrectly interpreted.

Neutralization is an abstract term for any technique that ensures that input (and output) conforms with expectations and is "safe." This can be done by:

- checking that the input/output is already "safe" (e.g. validation)

- transformation of the input/output to be "safe" using techniques such as filtering, encoding/decoding, escaping/unescaping, quoting/unquoting, or canonicalization

- preventing the input/output from being directly provided by an attacker (e.g. "indirect selection" that maps externally-provided values to internally-controlled values)

- preventing the input/output from being processed at all

This weakness typically applies in cases where the product prepares a control message that another process must act on, such as a command or query, and malicious input that was intended as data, can enter the control plane instead. However, this weakness also applies to more general cases where there are not always control implications.

Skutki

• Other

  Other

Słabości podrzędne

• CWE-20 Improper Input Validation
• CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
• CWE-116 Improper Encoding or Escaping of Output
• CWE-138 Improper Neutralization of Special Elements
• CWE-170 Improper Null Termination
• CWE-172 Encoding Error
• CWE-182 Collapse of Data into Unsafe Value
• CWE-228 Improper Handling of Syntactically Invalid Structure
• CWE-240 Improper Handling of Inconsistent Structural Elements
• CWE-463 Deletion of Data Structure Sentinel
• CWE-1426 Improper Validation of Generative AI Output

Kiedy powstaje

• Implementation — REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Not Technology-Specific

Uwagi

Concepts such as validation, data transformation, and neutralization are being refined, so relationships between CWE-20 and other entries such as CWE-707 may change in future versions, along with an update to the Vulnerability Theory document.