According to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Source code Weakness Analyzer Context-configured Source Code Weakness Analyzer
CWE-34 Variant Incomplete
Path Traversal: '....//'
This vulnerability occurs when an application builds file paths using user input but fails to properly sanitize '....//' sequences. Attackers can use this pattern to break out of the intended…
Definition
What is CWE-34?
This vulnerability occurs when an application builds file paths using user input but fails to properly sanitize '....//' sequences. Attackers can use this pattern to break out of the intended directory and access unauthorized files or folders elsewhere on the system.
The '....//' sequence is a specific evasion technique designed to bypass common path traversal filters. If a security mechanism removes or checks for '../' in a single pass, '....//' can be transformed into '../' after the filter runs, allowing the attack to succeed. This often happens with simple string replacement or certain regular expression implementations that don't account for this overlapping pattern.
Attackers use this method when applications try to neutralize '..' sequences or when the operating system treats double slashes ('//') as a single slash. Developers must validate entire canonical paths after normalization, rather than just filtering specific strings, to prevent these bypass attempts. Always resolve user-supplied paths to their absolute location and verify they remain within the permitted directory before any file operation.
Real-world impact
Real-world CVEs caused by CWE-34
-
Mail server allows remote attackers to create arbitrary directories via a ".." or rename arbitrary files via a "....//" in user supplied parameters.
How attackers exploit it
Step-by-step attacker path
- 1
Identify a code path that handles untrusted input without validation.
- 2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
- 3
Deliver the payload through a normal request and observe the application's reaction.
- 4
Iterate until the response leaks data, executes attacker code, or escalates privileges.
Vulnerable code example
Vulnerable pseudo
MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Secure code example
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist
How to prevent CWE-34
- Implementation Assume 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 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. This 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, denylists 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 allowlists 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 list 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 denylist, 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.
- Implementation 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 allowlist validation schemes by introducing dangerous inputs after they have been checked.
Detection signals
How to detect CWE-34
According to SOAR [REF-1479], the following detection techniques may be useful: ``` Highly cost effective: ``` Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.) Formal Methods / Correct-By-Construction
Plexicus auto-detects CWE-34 and opens a fix PR in under 60 seconds.
Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.
Frequently asked questions What is CWE-34?
How serious is CWE-34?
What languages or platforms are affected by CWE-34?
How can I prevent CWE-34?
How does Plexicus detect and fix CWE-34?
Where can I learn more about CWE-34?
Frequently asked questions
What is CWE-34?
This vulnerability occurs when an application builds file paths using user input but fails to properly sanitize '....//' sequences. Attackers can use this pattern to break out of the intended directory and access unauthorized files or folders elsewhere on the system.
How serious is CWE-34?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-34?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-34?
Assume 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 of acceptable values, missing or extra inputs, syntax, consistency across related fields, and…
How does Plexicus detect and fix CWE-34?
Plexicus's SAST engine matches the data-flow signature for CWE-34 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-34?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/34.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-34
CWE-23 Parent
Relative Path Traversal
This vulnerability occurs when an application builds file paths using user-supplied input without properly validating or sanitizing it.…
CWE-24 Sibling
Path Traversal: '../filedir'
Path traversal, often called directory traversal, occurs when an application builds a file path using user input without properly blocking…
CWE-25 Sibling
Path Traversal: '/../filedir'
This vulnerability, often called directory traversal, occurs when an application builds a file path using user input without properly…
CWE-26 Sibling
Path Traversal: '/dir/../filename'
This vulnerability occurs when an application builds a file path using user input but fails to properly block directory traversal…
CWE-27 Sibling
Path Traversal: 'dir/../../filename'
This vulnerability occurs when an application builds file paths using user input but fails to properly block sequences like…
CWE-28 Sibling
Path Traversal: '..\filedir'
This vulnerability occurs when an application builds a file path using user input but fails to block or properly handle '..\' sequences.…
CWE-29 Sibling
Path Traversal: '\..\filename'
This vulnerability occurs when an application builds file paths using user input but fails to block '\..\filename' sequences. Attackers…
CWE-30 Sibling
Path Traversal: '\dir\..\filename'
This vulnerability occurs when an application builds file paths using user input but fails to properly sanitize sequences like…
CWE-31 Sibling
Path Traversal: 'dir\..\..\filename'
This vulnerability occurs when an application builds file paths using user input but fails to properly block sequences like…
Resources
Further reading
- MITRE — official CWE-34 https://cwe.mitre.org/data/definitions/34.html
- State-of-the-Art Resources (SOAR) for Software Vulnerability Detection, Test, and Evaluation https://www.ida.org/-/media/feature/publications/s/st/stateoftheart-resources-soar-for-software-vulnerability-detection-test-and-evaluation/p-5061.ashx
Ready when you are
Don't Let Security
Weigh You Down.
Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.