Conversation
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.
Description
Mitigates PSB requirement
SEC-VAL-INEVAL-2for the public ISE Agent host tools. The requirement prohibits dynamically executing user-controlled commands or code and requires validation before untrusted values reach an interpreter.The launcher previously sourced the customer-editable
.envfile in Bash to readISE_AGENT_NETWORK_MODE. Shell substitutions or commands embedded in that file could therefore execute with the privileges of the user running the launcher. The update path also reusedAGENT_IDin Compose template rendering without revalidating a modified.env.This change:
.envvalues as plain data instead of sourcing the file;bridge/hostallowlist;AGENT_IDbefore it influences Compose template rendering;Why this satisfies SEC-VAL-INEVAL-2
The editable package configuration now crosses the shell trust boundary only through literal string parsing and explicit allowlists. It is never evaluated as Bash program text. Values that later influence an interpreter-like template operation are validated against the same constrained agent-ID grammar used during installation.
How Has This Been Tested?
bash -n agentctl tests/test-host-tools.shtests/test-host-tools.shTypes of Changes