CWE-289 使用候选名称进行的认证绕过
Authentication Bypass by Alternate Name
结构: Simple
Abstraction: Variant
状态: Incomplete
被利用可能性: unkown
基本描述
The software performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.
相关缺陷
-
cwe_Nature: ChildOf cwe_CWE_ID: 287 cwe_View_ID: 1000 cwe_Ordinal: Primary
-
cwe_Nature: ChildOf cwe_CWE_ID: 287 cwe_View_ID: 699 cwe_Ordinal: Primary
适用平台
Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}
常见的影响
| 范围 | 影响 | 注释 |
|---|---|---|
| Access Control | Bypass Protection Mechanism |
可能的缓解方案
MIT-44 Architecture and Design
策略: Input Validation
Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
MIT-5 Implementation
策略: Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a whitelist 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 (i.e., do not rely on a blacklist). A blacklist 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, blacklists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
MIT-20 Implementation
策略: Input Validation
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 whitelist validation schemes by introducing dangerous inputs after they have been checked.
分析过的案例
| 标识 | 说明 | 链接 |
|---|---|---|
| CVE-2003-0317 | Protection mechanism that restricts URL access can be bypassed using URL encoding. | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0317 |
| CVE-2004-0847 | Bypass of authentication for files using "\" (backslash) or "%5C" (encoded backslash). | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-0847 |
Notes
Relationship Overlaps equivalent encodings, canonicalization, authorization, multiple trailing slash, trailing space, mixed case, and other equivalence issues. Theoretical Alternate names are useful in data driven manipulation attacks, not just for authentication.
分类映射
| 映射的分类名 | ImNode ID | Fit | Mapped Node Name |
|---|---|---|---|
| PLOVER | Authentication bypass by alternate name | ||
| The CERT Oracle Secure Coding Standard for Java (2011) | IDS01-J | CWE More Specific | Normalize strings before validating them |
| SEI CERT Oracle Coding Standard for Java | IDS01-J | CWE More Specific | Normalize strings before validating them |