VariantDraft

CWE-176Improper Handling of Unicode Encoding

Category: other

Description

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

Common consequences· 1

  • Integrity — Unexpected State

Potential mitigations· 3

  • [Architecture and Design]Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
  • [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.

Related CAPEC attack patterns· 1

CAPEC-71

References

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

Exploits (incoming)1

TypeTargetConfidenceTier
AttackPatternUsing Unicode Encoding to Bypass Validation Logiccapec-71100%live

Related by meaning· 6

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

CWE
Improper Handling of Mixed Encoding
CWE
Improper Handling of Invalid Use of Special Elements
CWE
Improper Handling of URL Encoding (Hex Encoding)
CWE
Failure to Sanitize Paired Delimiters
CWE
Improper Neutralization of Input Leaders
CWE
Improper Handling of Inconsistent Special Elements
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.