fix: Potential fix for code scanning alert no. 5: Uncontrolled data used in path expression#20
Merged
Conversation
…n path expression Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Contributor
Reviewer's GuideAdds strict validation of path components used in Lambda code storage paths and propagates filesystem path resolution errors to fully address a code-scanning alert about uncontrolled data in path expressions. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Resolve conflicts in internal/services/lambda/store.go by keeping main's validPathComponent and filepath.Rel-based traversal detection, which already covers the path traversal fix from this branch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/skyoo2003/devcloud/security/code-scanning/5
To fix this without changing intended behavior, validate path components (
accountID,functionName) as single safe path segments before constructing filesystem paths.Best approach in this code:
internal/services/lambda/store.go, add a small validator method (for examplevalidatePathComponent) that rejects:"."/"..",/or\separators.codePathfor bothaccountIDandfunctionNamebeforefilepath.Join.filepath.Abserrors instead of ignoring them.This addresses all alert variants because they all converge on the same sink (
os.WriteFile(path, ...)) and same tainted source path.Suggested fixes powered by Copilot Autofix. Review carefully before merging.