Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-178 (大小写敏感处理不恰当) — Vulnerability Class 65

65 vulnerabilities classified as CWE-178 (大小写敏感处理不恰当). AI Chinese analysis included.

CWE-178 represents a logic flaw where software fails to properly account for case sensitivity when accessing or determining resource properties, leading to inconsistent and potentially insecure results. Attackers typically exploit this weakness by manipulating input casing to bypass access controls, evade input filters, or reduce the effective key space for password cracking, thereby facilitating brute-force attacks. For instance, a system treating "Admin" and "admin" as distinct users might inadvertently grant elevated privileges if case checks are inconsistently applied. To mitigate this risk, developers must enforce strict, consistent case-handling logic across all validation and authentication routines. This involves normalizing inputs to a standard case before comparison, explicitly defining case-sensitivity requirements in security policies, and rigorously testing edge cases to ensure that case variations do not circumvent security mechanisms or lead to unauthorized resource access.

MITRE CWE Description
The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. Improperly handled case sensitive data can lead to several possible consequences, including: case-insensitive passwords reducing the size of the key space, making brute force attacks easier bypassing filters or access controls using alternate names multiple interpretation errors using alternate names.
Common Consequences (1)
Access Control Bypass Protection Mechanism
Mitigations (3)
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…
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.
Examples (1)
In the following example, an XSS neutralization method intends to replace script tags in user-supplied input with a safe equivalent:
public String preventXSS(String input, String mask) { return input.replaceAll("script", mask); }
Bad · Java

Vulnerabilities classified as CWE-178 (大小写敏感处理不恰当) represent 65 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.