CWE-36: Absolute Path Traversal

BaseDraft

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as "/abs/path" that can resolve to a location that is outside of that directory.

View on MITRE
Back to CWE Lookup

Extended Description

This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-36 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-36, Absolute Path Traversal, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Apply Input Validation controls for Absolute Path Traversal

MITRE associates mitigation with Implementation, and Operation; the listed strategies include Input Validation, and Firewall; documented detection approaches include Automated Static Analysis. Use these source-defined anchors to turn CWE-36 into implementation, review, and verification checks for the affected component.

CWE-36: Absolute Path TraversalMITRE CWE

Triage CWE-36 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-36, Absolute Path Traversal, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-36

Apply MITRE's full root-cause mapping guidance when using CWE-36, Absolute Path Traversal. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-36 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-36, Absolute Path Traversal. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-36: Absolute Path Traversal?+

CWE-36: Absolute Path Traversal is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as "/abs/path" 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.

What are the security consequences of Absolute Path Traversal?+

If exploited, CWE-36 (Absolute Path Traversal) it can compromise Integrity, Confidentiality and Availability, leading to outcomes such as Execute Unauthorized Code or Commands, Modify Files or Directories, Read Files or Directories and DoS: Crash, Exit, or Restart.

Which programming languages are affected by Absolute Path Traversal?+

CWE-36 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Absolute Path Traversal?+

MITRE documents real CVEs mapped to CWE-36, including CVE-2024-0520, CVE-2022-31503, CVE-2002-1345, CVE-2001-1269 and CVE-2002-1818. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-36 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement