Security Resilience

CWE · MITRE source

CWE-29Path Traversal: '\..\filename'

Abstraction: Variant · CVEs in our corpus: 64

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.

This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory. This is similar to CWE-25, except using "\" instead of "/". Sometimes a program checks for "..\" at the beginning of the input, so a "\..\" can bypass that check. It is also useful for bypassing path traversal protection schemes that only assume that the "/" separator is valid.

Last updated: 19 November 2026 21:43 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: mostly · 14 mapping(s) from 4 framework(s): ATT&CK 6 (mostly) · ISO_IEC_27002_2022 5 (mostly) · 800-53 2 (mostly) · 1 (mostly)

See the full cumulative-coverage rollup →

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.PS-06
  • AC-4 Information Flow Enforcement
  • SI-10 Information Input Validation
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Our mappings

NIST 800-53 r5 controls PROPOSED for this weakness (0)

These are model PROPOSALS, not graded mappings. They come from controls_to_cwe_proposals, which carries no grade field at all; across the CWE pages 1,540 of 1,722 such associations (89%) have never been graded by anything. The heading said “address” until 2026-09-29, which asserted a relationship the data does not carry. Graded cross-walks are on the framework map, not here.

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.
Our mappings

MITRE ATT&CK techniques this weakness enables

Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing).

Direction: ← other covers this; → this covers other (F/M/P = full / mostly / partial). gov = governs / implements (a mandate, not coverage).

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2024-6396 9.49.80.53112024-07-12
CVE-2023-1177 9.29.30.69682023-03-24
CVE-2024-4320 8.99.80.34352024-06-06
CVE-2024-3429 8.89.80.28322024-06-06
CVE-2024-2083 8.79.90.37242024-04-16
CVE-2023-6909 8.47.50.89722023-12-18
CVE-2023-1034 8.08.80.26202023-02-25
CVE-2023-2780 8.09.80.06312023-05-17
CVE-2023-0104 7.99.30.21852023-02-22
CVE-2023-6975 7.79.80.02032023-12-20
CVE-2024-3848 7.77.50.43012024-05-16
CVE-2023-6021 7.67.50.37632023-11-16
CVE-2024-2360 7.69.80.01872024-06-06
CVE-2024-2624 7.69.80.01352024-06-06
CVE-2024-2358 7.59.80.01122024-05-16
CVE-2024-5443 7.59.80.01162024-06-22
CVE-2024-4322 7.47.50.30762024-05-16
CVE-2025-15036 7.410.00.00602026-03-30
CVE-2024-2928 7.27.50.21852024-06-06
CVE-2024-8537 7.19.10.01042025-03-20
CVE-2024-34470 7.08.60.06702024-05-06
CVE-2024-5926 7.09.10.00862024-06-30
CVE-2024-7957 7.09.10.00952025-03-20
CVE-2024-7774 6.99.10.00562024-10-29
CVE-2024-11170 6.98.80.01812025-03-20