fix: Potential fix for code scanning alert no. 8: Uncontrolled data used in path expression#17
Closed
skyoo2003 wants to merge 0 commit into
Closed
fix: Potential fix for code scanning alert no. 8: Uncontrolled data used in path expression#17skyoo2003 wants to merge 0 commit into
skyoo2003 wants to merge 0 commit into
Conversation
Contributor
Reviewer's GuideHardens Lambda function code path construction to prevent path traversal by validating path components and enforcing containment using normalized absolute paths and filepath.Rel. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
da78f7f to
885657b
Compare
885657b to
21a192e
Compare
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/8
General fix: validate untrusted path components before filesystem use, and enforce robust path containment checks with normalized absolute paths and
filepath.Rel(instead of simple prefix checks).Best concrete fix here:
internal/services/lambda/store.go, hardencodePath:functionName/accountIDcomponents (empty,".","..", any path separator),filepath.Reland reject ifrel == ".."or starts with".."+sep.code.ziplocation) for valid names.This addresses the CodeQL flow at the sink while preserving functionality for normal Lambda function names.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.