-
Notifications
You must be signed in to change notification settings - Fork 1
fix: address Mend SAST findings from #215 (4 of 5 High) #226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
peatey
wants to merge
4
commits into
develop
Choose a base branch
from
fix/mend-215-sast-findings
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
305b76d
fix(cldy): make SafePath actually prevent path traversal
peatey 5fa1bc0
fix(cldy): validate presigned upload destination before sending data
peatey d9a70d4
fix(bingen-to-json): tighten generated output permissions
peatey dd3f9ea
Merge branch 'develop' into fix/mend-215-sast-findings
peatey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -74,6 +74,48 @@ func TestSafePath(t *testing.T) { | |
| }, | ||
| want: "test/scratch/dirName/", | ||
| }, | ||
|
|
||
| // The following escaped the previous implementation, which deleted every | ||
| // literal ".." substring before cleaning. "...." collapses to ".." once the | ||
| // inner ".." is removed, which then resolves as a traversal. | ||
| "traversal via doubled dots": { | ||
| elements: []string{ | ||
| "test/scratch", | ||
| "....//....//etc/passwd", | ||
| }, | ||
| want: "test/scratch/..../..../etc/passwd", | ||
| }, | ||
| "traversal via dot-slash padding": { | ||
| elements: []string{ | ||
| "test/scratch", | ||
| "..././..././etc/shadow", | ||
| }, | ||
| want: "test/scratch/.../.../etc/shadow", | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why would we want this as a directory output? |
||
| }, | ||
| "traversal escaping the base is clamped": { | ||
| elements: []string{ | ||
| "test/scratch", | ||
| "../../../../etc/passwd", | ||
| }, | ||
| want: "test/scratch/etc/passwd", | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why are we avoiding conventional file pathing rules? |
||
| }, | ||
|
|
||
| // The previous implementation also mangled legitimate names containing | ||
| // consecutive dots, silently writing samples to the wrong directory. | ||
| "legitimate name with consecutive dots is preserved": { | ||
| elements: []string{ | ||
| "test/scratch", | ||
| "v1..2-cluster", | ||
| }, | ||
| want: "test/scratch/v1..2-cluster", | ||
| }, | ||
| "legitimate filename with consecutive dots is preserved": { | ||
| elements: []string{ | ||
| "test/scratch", | ||
| "my..cluster.tgz", | ||
| }, | ||
| want: "test/scratch/my..cluster.tgz", | ||
| }, | ||
| } | ||
| for name, tt := range tests { | ||
| t.Run(name, func(t *testing.T) { | ||
|
|
||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea what in the world this function is supposed to be doing. Why are we deleting segments that are
".."?I need to understand the semantics involved, and what is wrong with using
filepath.Jointo join file paths together, OR if we insist on doing some level of manipulation, usingfilepath.Cleanresolves all of the"."and".."usage in the paths.This just appears to be doing an absurd amount of work for no reason.