CWE-182: Collapse of Data into Unsafe Value
2 CVEs have CWE-182 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 0.665%.
The product filters data in a way that causes it to be reduced or collapsed into an unsafe value that violates an expected security property.
Child of CWE-790: Improper Filtering of Special Elements
Mitigations
- Architecture and Design: Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
- Implementation: Assume all input is malicious. Use an accept known good input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, boat may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as red or blue. Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However,…
- 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.
- Canonicalize the name to match that of the file system's representation of the name. This can sometimes be achieved with an available API (e.g. in Win32 the GetFullPathName function).
Observed examples
- CVE-2004-0815: /.//// in pathname collapses to absolute path.
- CVE-2005-3123: /.//..//////././ is collapsed into /.././ after .. and // sequences are removed.
- CVE-2002-0325: .../...// collapsed to ... due to removal of ./ in web server.
- CVE-2002-0784: Chain: HTTP server protects against .. but allows . variants such as ////./../.../. If the server removes /.. sequences, the result would collapse into an unsafe value ////../ (CWE-182).
- CVE-2005-2169: Chain: .../...// bypasses protection mechanism using regexp's that remove ../ resulting in collapse into an unsafe value ../ (CWE-182) and resultant path traversal.
- CVE-2001-1157: XSS protection mechanism strips a <script> sequence that is nested in another <script> sequence.
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-182'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-182'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).