BaseDraft

CWE-168Improper Handling of Inconsistent Special Elements

Category: other

Description

The product does not properly handle input in which an inconsistency exists between two or more special characters or reserved words. An example of this problem would be if paired characters appear in the wrong order, or if the special characters are not properly nested.

Common consequences· 1

  • Availability / Access Control / Non-Repudiation — DoS: Crash, Exit, or Restart, Bypass Protection Mechanism, Hide Activities

Potential mitigations· 3

  • []Developers should anticipate that inconsistent special elements will be injected/manipulated 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/168.html

Related by meaning· 6

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

CWE
Improper Handling of Invalid Use of Special Elements
CWE
Improper Handling of Syntactically Invalid Structure
CWE
Failure to Sanitize Paired Delimiters
CWE
Improper Handling of Unicode Encoding
CWE
Improper Neutralization of Input Leaders
CWE
Improper Handling of Additional Special Element
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.