fix: block path traversal in runtime file read/write paths#539
Merged
pradeeban merged 1 commit intoControlCore-Project:devfrom Apr 5, 2026
Merged
Conversation
Contributor
Author
|
@pradeeban @Rahuljagwani @mayureshkothare pls take a look, also added the same guard to legacy/sample runtime copies too, since they reuse the same file I/O path construction and would otherwise keep the traversal surface open. This should be good for consistency and safety across core and sample runtimes. |
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
2 participants
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.
Fixes #536
Runtime file I/O was trusting name when building port paths, so
../could escape the intended port directory. Added strict path-boundary checks before file reads/writes.changes:
Behavior change is only for invalid filenames. Valid workflows are unchanged.