CWE-39 路径遍历:'C:dirname'

Path Traversal: 'C:dirname'

结构: Simple

Abstraction: Variant

状态: Draft

被利用可能性: unkown

基本描述

An attacker can inject a drive letter or Windows volume letter ('C:dirname') into a software system to potentially redirect access to an unintended location or arbitrary file.

相关缺陷

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

  • cwe_Nature: ChildOf cwe_CWE_ID: 36 cwe_View_ID: 699 cwe_Ordinal: Primary

适用平台

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

常见的影响

范围 影响 注释
['Integrity', 'Confidentiality', 'Availability'] Execute Unauthorized Code or Commands The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity Modify Files or Directories The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality Read Files or Directories The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability DoS: Crash, Exit, or Restart The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the software from working at all and in the case of a protection mechanisms such as authentication, it has the potential to lockout every user of the software.

可能的缓解方案

MIT-5.1 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. When validating filenames, use stringent whitelists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a whitelist of allowable file extensions, which will help to avoid CWE-434. Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a blacklist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.

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-2001-0038 Remote attackers can read arbitrary files by specifying the drive letter in the requested URL. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2001-0038
CVE-2001-0255 FTP server allows remote attackers to list arbitrary directories by using the "ls" command and including the drive letter name (e.g. C:) in the requested pathname. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2001-0255
CVE-2001-0687 FTP server allows a remote attacker to retrieve privileged system information by specifying arbitrary paths. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2001-0687
CVE-2001-0933 FTP server allows remote attackers to list the contents of arbitrary drives via a ls command that includes the drive letter as an argument. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2001-0933
CVE-2002-0466 Server allows remote attackers to browse arbitrary directories via a full pathname in the arguments to certain dynamic pages. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-0466
CVE-2002-1483 Remote attackers can read arbitrary files via an HTTP request whose argument is a filename of the form "C:" (Drive letter), "//absolute/path", or ".." . https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-1483
CVE-2004-2488 FTP server read/access arbitrary files using "C:\" filenames https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-2488

分类映射

映射的分类名 ImNode ID Fit Mapped Node Name
PLOVER 'C:dirname' or C: (Windows volume or 'drive letter')
CERT C Secure Coding FIO05-C Identify files using multiple file attributes
Software Fault Patterns SFP16 Path Traversal