{"schemaVersion":"2.0.0","locale":"en","title":"Path traversal outside the extraction root","description":"Rule ID: security.path-traversal@1.0.0. Availability below refers to source-scan at product 524fa07e.","htmlUrl":"https://docs.swift-analyzer.com/catalog/security.path-traversal/","markdownUrl":"https://docs.swift-analyzer.com/catalog/security.path-traversal/index.md","productRevision":"524fa07e0ae4153c84ac12ae9eb6559df89ec2be","catalogRevision":"4558458d","docsRevision":"1f17ba58ab08627e0de898f1442067b09e960b48cd5605d6529e9275f8930d68","channel":"pre-prod","maturity":"experimental","access":"owner-provided-checkout","markdown":"# Path traversal outside the extraction root\n\nRule ID: security.path-traversal@1.0.0. Availability below refers to source-scan at product 524fa07e.\n\n## V-SEC-06 — Path traversal outside the extraction root\n\nPath traversal outside the extraction root. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects.\n\n### Availability\n\nNot available in source-scan. There is no source-scan flag to activate this condition.\n\n### Example and action\n\nIllustrative design scenario, not a runnable Swift example or a reproduced analyzer result. The stated availability and evidence boundaries still apply.\n\n**Before:** An archive entry such as ../outside.txt is joined to an extraction root without validating its destination.\n\nReview the following change against the contract and build variants described above.\n\n**After:** Use an extraction policy that rejects escaping paths and handles symlinks and path races. Validate the actual destination at the write boundary; a string-prefix comparison alone is insufficient.\n\n### Intended analysis\n\nIntended reasoning: Relate the selected security contract to a source, transformation and sensitive operation. The intended check requires identity, flow and policy evidence; a suspicious API name alone does not establish exploitation. Required evidence: source, sink, trust, policy, validation, and flow facts\n\n### Assumptions and unknown\n\nThe relevant facts must be admitted for the selected immutable build world. Unknown aliases, external effects, unsupported source forms or incomplete consumers can prevent a conclusion. Availability in this workflow is stated above; the illustration does not expand that availability.\n\n### Evidence and interpretation\n\nThe target catalog describes the intended condition. It is not evidence of an active source-scan diagnostic.\n\nHistorical evidence at 4558458d: recovery-required (historical qualification is incomplete and needs further evidence). That evidence has not been requalified for this product revision.\n\n[How we validate checks](https://docs.swift-analyzer.com/concepts/validation/) explains the evidence boundary. [Foundations](https://docs.swift-analyzer.com/concepts/foundations/) separates method assumptions from implementation claims.\n","anchors":["path-traversal-outside-the-extraction-root","V-SEC-06","availability","example-and-action","intended-analysis","assumptions-and-unknown","evidence-and-interpretation"]}