BaseIncomplete
CWE-179Incorrect Behavior Order: Early Validation
Category: other
Description
The product 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.
Product needs to validate data at the proper time, after data has been canonicalized and cleansed. Early validation is susceptible to various manipulations that result in dangerous inputs that are produced by canonicalization and cleansing.
Common consequences· 1
- Access Control / Integrity — Bypass Protection Mechanism, Execute Unauthorized Code or CommandsAn attacker could include dangerous input that bypasses validation protection mechanisms which can be used to launch various attacks including injection attacks, execute arbitrary code or cause other unintended behavior.
Potential mitigations· 1
- [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· 3
References
Exploits (incoming)3
| Type | Target | Confidence | Tier |
|---|---|---|---|
| AttackPattern | Using Leading 'Ghost' Character Sequences to Bypass Input Filterscapec-3 | 100% | live |
| AttackPattern | Exploiting Multiple Input Interpretation Layerscapec-43 | 100% | live |
| AttackPattern | Using Unicode Encoding to Bypass Validation Logiccapec-71 | 100% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.