BaseDraft

CWE-166Improper Handling of Missing Special Element

Category: other

Description

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

Common consequences· 1

  • Availability — DoS: Crash, Exit, or Restart

Potential mitigations· 3

  • []Developers should anticipate that special elements will be removed in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.
  • [Implementation]
  • [Implementation]Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.

References

  1. https://cwe.mitre.org/data/definitions/166.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Improper Handling of Additional Special Element
CWE
Failure to Handle Incomplete Element
CWE
Improper Filtering of Special Elements
CWE
Incomplete Filtering of One or More Instances of Special Elements
CWE
Incomplete Filtering of Special Elements
CWE
Incomplete Filtering of Multiple Instances of Special Elements
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.