Potential fix for code scanning alert no. 2: Uncontrolled command line#13
Merged
Rootless-Ghost merged 1 commit intomasterfrom Apr 25, 2026
Merged
Potential fix for code scanning alert no. 2: Uncontrolled command line#13Rootless-Ghost merged 1 commit intomasterfrom
Rootless-Ghost merged 1 commit intomasterfrom
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
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/Rootless-Ghost/AtomicLoop/security/code-scanning/2
The best fix is to ensure only commands that are explicitly allowlisted by executor are accepted from the HTTP API, and reject anything else before calling execution routines. This preserves functionality (running known atomic commands) while preventing arbitrary user-supplied command content from reaching subprocess interpreters.
Implement this in
app.pyin the request handler shown (around lines 239–276):_is_allowed_atomic_commandfromcore.executoralongsideexecute.command/executor_typeand validatingcommandis non-empty, add a guard:_is_allowed_atomic_command(command, executor_type)is false, return400with a clear error.This is the least invasive change, keeps existing behavior for valid atomic commands, and adds a clear sanitization/validation step on untrusted input path so the sink is no longer directly fed arbitrary request data.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.