目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1000

100.0%

CWE-22 对路径名的限制不恰当(路径遍历) 类漏洞列表 3481

CWE-22 对路径名的限制不恰当(路径遍历) 类弱点 3481 条 CVE 漏洞汇总,含 AI 中文分析。

CWE-22 属于路径遍历漏洞,指程序未正确过滤外部输入中的特殊字符,导致构造的文件路径突破受限目录限制。攻击者常利用“../”等序列访问系统敏感文件,窃取数据或执行恶意操作。开发者应严格校验输入,使用白名单机制限制合法字符,并采用绝对路径或规范化处理,确保最终解析路径始终位于预期目录内,从而有效防御此类风险。

MITRE CWE 官方描述
CWE:CWE-22 对受限目录的路径名限制不当('Path Traversal') 英文:产品使用外部输入来构造一个路径名,该路径名旨在标识位于受限父目录下的文件或目录,但产品未能正确中和路径名中可能导致路径名解析到受限目录之外位置的特殊元素。 许多文件操作旨在在受限目录内进行。通过使用“..”和“/”分隔符等特殊元素,攻击者可以逃逸出受限位置,以访问系统中其他位置的文件或目录。最常见的特殊元素之一是“../”序列,在大多数现代操作系统中,它被解释为当前位置的父目录。这被称为相对路径遍历(relative path traversal)。路径遍历(Path Traversal)也涵盖使用绝对路径名(如“/usr/local/bin”)来访问意外文件的情况。这被称为绝对路径遍历(absolute path traversal)。
常见影响 (4)
Integrity, Confidentiality, AvailabilityExecute 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.
IntegrityModify 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 …
ConfidentialityRead 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 a…
AvailabilityDoS: 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 product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
缓解措施 (5)
ImplementationAssume 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…
Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
ImplementationInputs 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. Use a built-in path canonicalization function (such as realpath(…
Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
OperationUse an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
Effectiveness: Moderate
代码示例 (2)
The following code could be for a social networking application in which each user's profile information is stored in a separate file. All files are stored in a single directory.
my $dataPath = "/users/cwe/profiles"; my $username = param("user"); my $profilePath = $dataPath . "/" . $username; open(my $fh, "<", $profilePath) || ExitError("profile read error: $profilePath"); print "<ul>\n"; while (<$fh>) { print "<li>$_</li>\n"; } print "</ul>\n";
Bad · Perl
../../../etc/passwd
Attack
In the example below, the path to a dictionary file is read from a system property and used to initialize a File object.
String filename = System.getProperty("com.domain.application.dictionaryFile"); File dictionaryFile = new File(filename);
Bad · Java
CVE ID标题CVSS风险等级Published
CVE-2025-43889 Dell PowerProtect Data Domain 路径遍历漏洞 — PowerProtect Data Domain with Data Domain Operating System (DD OS) of Feature Release 5.3 Medium2025-10-07
CVE-2025-43934 Dell PowerProtect Data Domain 路径遍历漏洞 — PowerProtect Data Domain with Data Domain Operating System (DD OS) of Feature Release 6.0 Medium2025-10-07
CVE-2025-40889 Nozomi Networks Guardian和Nozomi Networks CMC 路径遍历漏洞 — Guardian 8.1 High2025-10-07
CVE-2025-3718 Nozomi Networks CMC 路径遍历漏洞 — Guardian 7.9 High2025-10-07
CVE-2025-11337 Four-Faith Water Conservancy Informatization Platform 路径遍历漏洞 — Water Conservancy Informatization Platform 5.3 Medium2025-10-06
CVE-2025-11336 Four-Faith Water Conservancy Informatization Platform 路径遍历漏洞 — Water Conservancy Informatization Platform 5.3 Medium2025-10-06
CVE-2025-58591 SICK AG Baggage Analytics 安全漏洞 — Baggage Analytics 6.5 Medium2025-10-06
CVE-2025-58590 SICK AG Baggage Analytics 安全漏洞 — Baggage Analytics 6.5 Medium2025-10-06
CVE-2025-8917 clearml 安全漏洞 — allegroai/clearml 9.8AICriticalAI2025-10-05
CVE-2025-8406 ZenML 安全漏洞 — zenml-io/zenml 9.8AICriticalAI2025-10-05
CVE-2025-47211 QNAP operating system 路径遍历漏洞 — QTS 6.5 -2025-10-03
CVE-2025-33034 QNAP Qsync Central 路径遍历漏洞 — Qsync Central 7.5 -2025-10-03
CVE-2025-61666 Traccar 安全漏洞 — traccar 9.1AICriticalAI2025-10-02
CVE-2025-59744 AndSoft e-TMS 路径遍历漏洞 — e-TMS 5.3 -2025-10-02
CVE-2025-54293 LXD 安全漏洞 — LXD 6.5AIMediumAI2025-10-02
CVE-2025-54292 LXD 安全漏洞 — LXD 8.1AIHighAI2025-10-02
CVE-2025-11221 GTONE ChangeFlow 安全漏洞 — ChangeFlow 8.8 High2025-10-02
CVE-2025-11182 GTONE ChangeFlow 安全漏洞 — ChangeFlow 6.5 Medium2025-10-02
CVE-2025-58769 Auth0-PHP 安全漏洞 — laravel-auth0 3.3 Low2025-10-01
CVE-2025-11233 Rust 安全漏洞 — std 9.8AICriticalAI2025-10-01
CVE-2025-8559 WordPress plugin All in One Music Player 路径遍历漏洞 — All in One Music Player 6.5 Medium2025-09-30
CVE-2025-61586 FreshRSS 安全漏洞 — FreshRSS 5.3 -2025-09-29
CVE-2025-43813 Liferay Portal和Liferay DXP 路径遍历漏洞 — Portal 8.2AIHighAI2025-09-29
CVE-2025-11139 Bjskzy Zhiyou ERP 路径遍历漏洞 — Zhiyou ERP 6.3 Medium2025-09-29
CVE-2025-11034 Dibo Data Decision Making System 路径遍历漏洞 — Data Decision Making System 4.3 Medium2025-09-26
CVE-2025-11031 DataTables 安全漏洞 — DataTables 5.3 Medium2025-09-26
CVE-2025-11018 Four-Faith Water Conservancy Informatization Platform 路径遍历漏洞 — Water Conservancy Informatization Platform 5.3 Medium2025-09-26
CVE-2025-11016 kodbox 路径遍历漏洞 — kodbox 4.3 Medium2025-09-26
CVE-2025-59002 WordPress plugin BM Content Builder 路径遍历漏洞 — BM Content Builder 7.7 High2025-09-26
CVE-2025-10307 WordPress plugin Backuply 路径遍历漏洞 — Backuply – Backup, Restore, Migrate and Clone 6.5 Medium2025-09-26

CWE-22(对路径名的限制不恰当(路径遍历)) 是常见的弱点类别,本平台收录该类弱点关联的 3481 条 CVE 漏洞。