forked from NousResearch/hermes-agent
-
Notifications
You must be signed in to change notification settings - Fork 0
fix(security): strip dynamic Hermes secrets (AUXILIARY_*/GATEWAY_RELAY_*) from all subprocess spawn env + route codex through hermes_subprocess_env #213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Explicit docker_forward_env keys bypass _is_hermes_internal_secret filtering (security)
In tools/environments/docker.py, _build_init_env_args applies _is_hermes_internal_secret filtering only to implicit passthrough keys derived from get_all_passthrough(), but NOT to explicit forward keys from self._forward_env (docker_forward_env config). The is_hermes_internal_secret predicate (tools/environments/local.py:211-253) is documented as the single source of truth for stripping AUXILIARY_API_KEY/BASE_URL and GATEWAY_RELAY_SECRET/_KEY/_TOKEN secrets 'unconditionally regardless of env_passthrough skill registration or inherit_credentials' across every spawn path. The local subprocess sanitizer (_sanitize_subprocess_env, local.py:280-281) enforces this by checking every key against _is_hermes_internal_secret before passthrough logic. The Docker path breaks this contract for explicit forward keys — line 1004 unions explicit_forward_keys directly into forward_keys without any _is_hermes_internal_secret check. A user who adds e.g. GATEWAY_RELAY_SESSION_TOKEN to docker_forward_env in config.yaml would have that relay-auth secret injected via docker exec -e into the container's init_session snapshot.
💡 Suggestion: Apply _is_hermes_internal_secret to both explicit and implicit forward keys by filtering the union through a set comprehension that checks _is_hermes_internal_secret on every key. Update the comment at lines 996-1000 to note that explicit opt-in wins over the name-based blocklist (_HERMES_PROVIDER_ENV_BLOCKLIST) but NOT over the unconditional internal-secret predicate.
📋 Prompt for AI Agents
In tools/environments/docker.py, _build_init_env_args method (line 1004), change:
forward_keys = explicit_forward_keys | (_implicit_forward - _HERMES_PROVIDER_ENV_BLOCKLIST)
to:
forward_keys = {k for k in (explicit_forward_keys | (_implicit_forward - _HERMES_PROVIDER_ENV_BLOCKLIST)) if not _is_hermes_internal_secret(k)}
Also update the comment at lines 996-1000 to note that explicit opt-in does not override _is_hermes_internal_secret stripping.