Fix potential path traversal vulnerability during bundle extraction#1882
Merged
Conversation
Added `Path.GetFullPath` validation in `BundleFile.cs` when extracting Unity bundle files to disk. This ensures that maliciously crafted bundle files with directory traversal characters (`../`) in their filenames cannot write arbitrary files outside the intended `_unpacked` target directory. This addresses the valid portion of the "Zip Slip" Code Scanning alert.
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
1 participant
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.
Added
Path.GetFullPathvalidation inBundleFile.cswhen extracting Unity bundle files to disk. This ensures that maliciously crafted bundle files with directory traversal characters (../) in their filenames cannot write arbitrary files outside the intended_unpackedtarget directory. This addresses the valid portion of the "Zip Slip" Code Scanning alert.