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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-22 (对路径名的限制不恰当(路径遍历)) — Vulnerability Class 3484

3484 vulnerabilities classified as CWE-22 (对路径名的限制不恰当(路径遍历)). AI Chinese analysis included.

CWE-22 represents a critical input validation weakness where software fails to properly sanitize external input before constructing file paths. Attackers typically exploit this vulnerability by injecting directory traversal sequences, such as “../”, into user-supplied parameters. These malicious inputs allow the application to resolve file references outside the intended restricted directory, potentially granting unauthorized access to sensitive system files, configuration data, or source code. To mitigate this risk, developers must implement rigorous input validation techniques, ensuring that all path components are strictly checked against allowed characters and structures. Additionally, employing canonicalization to resolve symbolic links and relative paths before validation, combined with strict chroot jails or sandboxing, effectively confines file operations to designated directories, thereby neutralizing the potential for path traversal attacks and preserving system integrity.

MITRE CWE Description
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Many file operations are intended to take place within a restricted directory. By using special elements such as ".." and "/" separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the "../" sequence, which in most modern operating systems is interpreted as the parent directory of the current location. This is referred to as relative path traversal. Path traversal also covers the use of absolute pathnames such as "/usr/local/bin" to access unexpected files. This is referred to as absolute path traversal.
Common Consequences (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.
Mitigations (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
Examples (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 IDTitleCVSSSeverityPublished
CVE-2025-10232 299ko FileManagerAPIController.php delete path traversal — 299ko 5.4 Medium2025-09-10
CVE-2025-41714 Path Traversal via 'Upload-Key' in SmartEMS Upload Handling — SmartEMS Web Application 8.8 High2025-09-10
CVE-2025-23343 NVIDIA NVDebug 路径遍历漏洞 — NVDebug tool 7.6 High2025-09-09
CVE-2025-34176 Netgate pfSense CE Suricata Package v7.0.8_2 Directory Traversal Information Disclosure — pfSense CE 4.3AIMediumAI2025-09-09
CVE-2025-34173 Netgate pfSense CE Snort package v4.1.6_25 Directory Traversal Information Disclosure — pfSense CE 4.3AIMediumAI2025-09-09
CVE-2025-47415 RECWAVE Filepath Traversal — TOUCHSCREENS x60, x70 series 7.5AIHighAI2025-09-09
CVE-2025-54261 ColdFusion | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22) — ColdFusion 10.0 Critical2025-09-09
CVE-2025-58755 MONAI has path traversal issue that may lead to arbitrary file writes — MONAI 8.8 High2025-09-08
CVE-2025-58751 Vite middleware may serve files starting with the same name with the public directory — vite 5.3AIMediumAI2025-09-08
CVE-2025-5993 Path Traversal in ITCube CRM — ITCube CRM 7.5AIHighAI2025-09-08
CVE-2025-58438 internetarchive is vulnerable to Directory Traversal through file downloads — internetarchive 8.8AIHighAI2025-09-06
CVE-2025-9566 Podman: podman kube play command may overwrite host files 8.1 High2025-09-05
CVE-2025-48395 Eaton NMC G2 安全漏洞 — NMC G2 4.7 Medium2025-09-05
CVE-2025-41035 Path Traversal vulnerability in appRain CMF — appRain CMF 6.5 -2025-09-04
CVE-2025-58355 Soft Serve is vulnerable to arbitrary file writing through its SSH API — soft-serve 7.7 High2025-09-03
CVE-2025-7039 Glib: buffer under-read on glib through glib/gfileutils.c via get_tmp_file() — Red Hat Enterprise Linux 10 3.7 Low2025-09-03
CVE-2025-7975 Anritsu ShockLine CHX File Parsing Directory Traversal Remote Code Execution Vulnerability — ShockLine 7.8 -2025-09-02
CVE-2025-58162 MobSF Vulnerable to Arbitrary File Write (AR-Slip) via Absolute Path in .a Extraction — Mobile-Security-Framework-MobSF 6.5 Medium2025-09-02
CVE-2025-58161 MobSF Path Traversal in GET /download/<filename> using absolute filenames — Mobile-Security-Framework-MobSF 6.5AIMediumAI2025-09-02
CVE-2025-9801 SimStudioAI sim path traversal — sim 5.4 Medium2025-09-01
CVE-2025-58158 Harness Affected by Arbitrary File Write in Gitness LFS server — harness 8.8 High2025-08-29
CVE-2025-52861 VioStor — VioStor 6.5 -2025-08-29
CVE-2025-33038 Qsync Central — Qsync Central 7.5 -2025-08-29
CVE-2025-33037 Qsync Central — Qsync Central 7.5 -2025-08-29
CVE-2025-33036 Qsync Central — Qsync Central 7.5 -2025-08-29
CVE-2025-33033 Qsync Central — Qsync Central 7.5 -2025-08-29
CVE-2025-33032 QTS, QuTS hero — QTS 4.9 -2025-08-29
CVE-2025-30271 QTS, QuTS hero — QTS 6.5 -2025-08-29
CVE-2025-30270 QTS, QuTS hero — QTS 6.5 -2025-08-29
CVE-2025-9650 yeqifu carRental AppFileUtils.java removeFileByPath path traversal — carRental 5.4 Medium2025-08-29

Vulnerabilities classified as CWE-22 (对路径名的限制不恰当(路径遍历)) represent 3484 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.