Potential fix for code scanning alert no. 6: Arbitrary file access during archive extraction ("Zip Slip") - #10
Merged
Merged
Conversation
…ring archive extraction ("Zip Slip")
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
ShadowDara
marked this pull request as ready for review
September 9, 2026 15:01
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/ShadowDara/finder/security/code-scanning/6
To fix Zip Slip safely, validate each archive entry name before any filesystem operation, then continue using the existing resolved-within-root check as defense in depth.
Best single fix in
internal/bt/gitrepo/gitrepo.go(insiderestoreZiploop):file.Name:filepath.Clean(filepath.FromSlash(file.Name))filepath.IsAbs(...)andfilepath.VolumeName(...) != "")..traversal segments using segment-aware checks (not just substring)filepath.Join(destination, cleanedName).resolvedunderroot) intact.This addresses both CodeQL variants at line 420 and 427 because tainted, unvalidated names no longer reach directory creation or file creation paths.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.