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.

Auswirkungen in der Praxis

Real-world CVEs caused by CWE-34

CVE-2004-1670

Mail server allows remote attackers to create arbitrary directories via a ".." or rename arbitrary files via a "....//" in user supplied parameters.

Wie Angreifer es ausnutzen

Angreiferpfad Schritt für Schritt

1
Identifiziere einen Codepfad, der nicht vertrauenswürdige Eingaben ohne Validierung verarbeitet.
2
Erzeuge eine Payload, die das unsichere Verhalten auslöst — Injection, Traversal, Overflow oder Logik-Missbrauch.
3
Liefere die Payload über einen normalen Request aus und beobachte die Reaktion der Anwendung.
4
Iteriere, bis die Antwort Daten preisgibt, Angreifer-Code ausführt oder Berechtigungen eskaliert.

Verwundbares Codebeispiel

Vulnerable pseudo

MITRE hat kein Codebeispiel für diese CWE veröffentlicht. Das untenstehende Muster ist illustrativ — kanonische Referenzen findest du unter Ressourcen.

Verwundbar pseudo

// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}

Sicheres Codebeispiel

Secure pseudo

Sicher 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.

Präventions-Checkliste

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.

Erkennungssignale

How to detect CWE-34

Automated Static Analysis - Source Code SOAR Partial

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

Architecture or Design Review High

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-Fix

Plexicus erkennt CWE-34 automatisch und öffnet in unter 60 Sekunden einen Fix-PR.

Codex Remedium scannt jeden Commit, identifiziert genau diese Schwachstelle und liefert einen reviewer-ready Pull Request mit dem Patch. Keine Tickets. Keine Hand-offs.

Demo anfordern Plexicus kostenlos testen

Häufig gestellte Fragen

Frequently asked questions

Was ist CWE-34?

Wie gravierend ist CWE-34?

MITRE hat für diese Schwachstelle keine Exploit-Wahrscheinlichkeit veröffentlicht. Behandle sie als mittlere Auswirkung, bis dein Threat Model anderes belegt.

Welche Sprachen oder Plattformen sind von CWE-34 betroffen?

MITRE hat für diese CWE keine betroffenen Plattformen spezifiziert — sie kann in den meisten Anwendungs-Stacks auftreten.

Wie kann ich CWE-34 verhindern?

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…

Wie erkennt und behebt Plexicus CWE-34?

Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-34 bei jedem Commit. Bei einem Treffer öffnet unser Codex-Remedium-Agent einen Fix-PR mit korrigiertem Code, Tests und einer einzeiligen Zusammenfassung für den Reviewer.

Wo erfahre ich mehr über CWE-34?

MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/34.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.

Verwandte Schwachstellen

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'