CWE-428 未经引用的搜索路径或元素

Unquoted Search Path or Element

结构: Simple

Abstraction: Base

状态: Draft

被利用可能性: unkown

基本描述

The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path.

扩展描述

If a malicious individual has access to the file system, it is possible to elevate privileges by inserting such a file as "C:\Program.exe" to be run by a privileged program making use of WinExec.

相关缺陷

  • cwe_Nature: ChildOf cwe_CWE_ID: 668 cwe_View_ID: 1000 cwe_Ordinal: Primary

  • cwe_Nature: ChildOf cwe_CWE_ID: 668 cwe_View_ID: 1003 cwe_Ordinal: Primary

适用平台

Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}

Operating_System: [{'cwe_Name': 'Windows NT', 'cwe_Prevalence': 'Sometimes'}, {'cwe_Name': 'macOS', 'cwe_Prevalence': 'Rarely'}]

常见的影响

范围 影响 注释
['Confidentiality', 'Integrity', 'Availability'] Execute Unauthorized Code or Commands

可能的缓解方案

Implementation

策略:

Properly quote the full search path before executing a program on the system.

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.

示例代码

例

The following example demonstrates the weakness.

bad C

UINT errCode = WinExec( "C:\Program Files\Foo\Bar", SW_SHOW );

分析过的案例

标识 说明 链接
CVE-2005-1185 Small handful of others. Program doesn't quote the "C:\Program Files\" path when calling a program to be executed - or any other path with a directory or file whose name contains a space - so attacker can put a malicious program.exe into C:. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-1185
CVE-2005-2938 CreateProcess() and CreateProcessAsUser() can be misused by applications to allow "program.exe" style attacks in C: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-2938
CVE-2000-1128 Applies to "Common Files" folder, with a malicious common.exe, instead of "Program Files"/program.exe. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-1128

Notes

Applicable Platform

Maintenance

Research Gap Under-studied, probably under-reported.

分类映射

映射的分类名 ImNode ID Fit Mapped Node Name
PLOVER Unquoted Search Path or Element

引用