What does path traversal cover in practice?
path traversal: The practical scope is Detect request paths escaping an intended directory boundary.. Start with the listed entities or files and confirm the result on representative code.
Detect path traversal before merge.
See how path traversal fits local review, which evidence Code Radar produces, where coverage ends, and how trusted findings move into CI.
radar scan . --quickWhat path traversal means here.
The path traversal rule identifies review patterns that can create exploitable behavior or hide material maintenance risk, then returns the affected location, severity, confidence, and remediation context.
Rule reference
Evidence to inspect
Verify the input scope, finding detail, workflow handoff, and product boundary before you install or buy.
CriterionEvidence to inspectBoundary
Input scopeSelected files, configuration, scan mode, and enabled rules.Only included paths and configured checks are evaluated.
Finding detailFile, line, rule ID, severity, explanation, and repair direction.Illustrative output is not a result from your repository.
Workflow handoffLocal result, report format, agent context, and optional CI signal.Enable exports or CI only when the workflow needs them.
Decision fitUse the same criteria on a real repository before choosing a plan or tool.No universal winner or guaranteed outcome is claimed.
Rule reference
Check this risk locally
Verify the input scope, finding detail, workflow handoff, and product boundary before you install or buy.
The problem this page helps clarify
The useful question is where path traversal changes the review loop: what enters the scan, who acts on a finding, and which evidence moves forward. Detect request paths escaping an intended directory boundary.
- Audience: Developers and reviewers deciding how to handle path traversal findings before merge.
- Focus: Detect request paths escaping an intended directory boundary.
- Review question: What does path traversal cover in practice?
Coverage and concrete signals
For path traversal, inspect the concrete scope below instead of relying on a category label. Check how request paths are resolved against the base directory and verify that the safer example rejects paths outside that boundary.
- Focus: Detect request paths escaping an intended directory boundary.
- Workflow: Rule ID: RADAR-SEC-PATH
- Coverage and concrete signals: RADAR-SEC-PATH, unsafe pattern, safer pattern, Source security
FocusExact file location, rule context, severity, confidence, and remediation guidance.Boundary
Detect request paths escaping an intended directory boundary.Check how request paths are resolved against the base directory and verify that the safer example rejects paths outside that boundary.A trusted identifier or a resolver that canonicalizes and enforces containment can avoid a finding; verify symlink and encoded-path cases before suppressing.
Risky pattern / Safer pattern
path traversal: A useful result must be explainable to a developer and portable to the next review surface. Inspect the concrete evidence below before changing team policy.
Risky patternSafer pattern
readFile(baseDir + request.path);readFile(resolveInside(baseDir, request.path));
From local signal to shared gate.
path traversal: Use the smallest workflow that proves value. Each later step should reuse evidence the team already understands. Detect request paths escaping an intended directory boundary.
StepCommand or actionDecision
1Run a quick local scanIs the signal useful?
2Inspect and repair findingsIs the fix specific and reproducible?
3Export portable evidenceDoes the reviewer need SARIF, JSON, or HTML?
4Promote the trusted threshold to CIWhich severity should block a pull request?
radar scan . --quick
radar scan . --format sarif --fail-on highEvidence to inspect before you trust the result.
path traversal: A useful result must be explainable to a developer and portable to the next review surface. Inspect the concrete evidence below before changing team policy. Check how request paths are resolved against the base directory and verify that the safer example rejects paths outside that boundary.
- Rule ID: RADAR-SEC-PATH
- Exact file location, rule context, severity, confidence, and remediation guidance.
- Terminal output, SARIF, JSON, or HTML artifacts generated from the same finding set.
- Source stays in the workspace or CI runner where the scan executes.
Good fit and limits
Use path traversal when Developers and reviewers deciding how to handle path traversal findings before merge. Keep the boundary explicit: A trusted identifier or a resolver that canonicalizes and enforces containment can avoid a finding; verify symlink and encoded-path cases before suppressing.
Run the local proof before adopting a shared gate.
- Good fit: Developers and reviewers deciding how to handle path traversal findings before merge.
- Not a fit / do not overreach: A trusted identifier or a resolver that canonicalizes and enforces containment can avoid a finding; verify symlink and encoded-path cases before suppressing.
Questions to verify before rollout
These questions keep the decision tied to observable evidence rather than a broad product promise.
Which evidence should I inspect for path traversal?
path traversal: Inspect Check how request paths are resolved against the base directory and verify that the safer example rejects paths outside that boundary. Keep the source location, rule or comparison context, and exported artifact together.
What should I not infer from path traversal?
path traversal: Do not infer universal coverage. A trusted identifier or a resolver that canonicalizes and enforces containment can avoid a finding; verify symlink and encoded-path cases before suppressing. Use the relevant comparison or workflow page to test the boundary before changing policy.
What should I try first for path traversal?
path traversal: Start with a local run, review one real finding, then choose the linked report, agent, CI, or trust workflow that matches the next decision.
Validate the workflow on your own code.
Start with one local scan, inspect the evidence, and expand to reports, agents, or CI only when the signal is useful.