Skip to content

[Aikido] AI Fix for Path traversal attack possible - #61

Closed
aikido-autofix[bot] wants to merge 1 commit into
mainfrom
fix/aikido-security-sast-190122962-acdt
Closed

aikido-autofix[bot] wants to merge 1 commit into
mainfrom
fix/aikido-security-sast-190122962-acdt

Conversation

@aikido-autofix

Copy link
Copy Markdown

This patch mitigates path traversal vulnerability by validating the wavPath parameter to reject paths containing ".." before the File.OpenRead sink executes.

✅ 1 issue fixed by this PR, including 1 critical 🚨 issue
Issue Severity           Description
Sast#1028212507
🚨 CRITICAL
A malicious actor could control the location of this file, to include going backwards up a directory by adding '../' to the input.

High confidence: Aikido has a robust set of benchmarks for similar fixes, and they are proven to be effective.

@sonarqubecloud

Copy link
Copy Markdown

@manuc66

manuc66 commented Nov 19, 2026

Copy link
Copy Markdown
Owner

Superseded by 35f5267 on main. The finding was triaged rather than patched: a library reads the file its caller names, and the caller already holds the same filesystem rights, so rejecting '..' fixes nothing and breaks legitimate relative paths (e.g. passing ../audio.wav). SECURITY.md now records the contract, and the build tooling that did need a boundary is confined to the tree it owns (src/Shared/BuildPath.cs).

@manuc66 manuc66 closed this Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant