VariantDraft
CWE-177Improper Handling of URL Encoding (Hex Encoding)
Category: other
Description
The product does not properly handle when all or part of an input has been URL encoded.
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· 4
References
Exploits (incoming)4
| Type | Target | Confidence | Tier |
|---|---|---|---|
| AttackPattern | Double Encodingcapec-120 | 100% | live |
| AttackPattern | Using Slashes and URL Encoding Combined to Bypass Validation Logiccapec-64 | 100% | live |
| AttackPattern | URL Encodingcapec-72 | 100% | live |
| AttackPattern | Generic Cross-Browser Cross-Domain Theftcapec-468 | 100% | live |
(incoming)3
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Vulnerability | CVE-2026-22031cve-2026-22031 | 0% | live |
| Vulnerability | CVE-2026-22037cve-2026-22037 | 0% | live |
| Vulnerability | CVE-2026-29045cve-2026-29045 | 0% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.