Add CWE-22 path traversal test case (Go) - #175
Merged
ralyodio merged 8 commits intoAug 17, 2026
Merged
Conversation
Contributor
Author
|
Sixth submission for the uGig listing: Go CWE-22 path-traversal case (2 VULNERABLE: + 1 SAFE:). |
…asses api.example.com resolves, which trips safety rule 3 (no resolvable network destinations). Switch to api.example.invalid (RFC 2606) and correct the @safe-guard text, which claimed no hosts were referenced. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Regenerated the catalog rather than hand-resolving it, which is the only resolution that cannot silently drop an entry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
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.
Test Case Submission
docs/CONTRIBUTING.mdif neverRun+//go:build ignore)VULNERABLE:and correct-code lines withSAFE:Details
filepath.Joinwith request inputhttp.ServeFileandos.ReadFilewith a tainted filename and a broken exact-prefix guard(
strings.HasPrefixon the joined path, defeated by../..), plus afilepath.Clean-basedSAFE:control.
Safety statement
The whole file is behind
//go:build ignoreand theneverRunconstant, so it can never be built orrun. No file is opened, no path resolved, and there are no hosts or credentials.
Scanner result
Leave blank on submission — CI fills this in.