Don't allow secrets to be extracted without approval - #135
Merged
Conversation
Secrets -o yaml and config --raw are leaking secrets that should be generally sealed in the cluster so don't allow those by default. Also rethinks how sometimes-safe commands are treated: commands with opaque tokens (command substitutions, parameter expansions, indirect expansions) that could alter security-sensitive arguments are conservatively blocked. Handlers receive opaque_positions so they can detect when runtime-determined values bypass static checks.
This was referenced Jun 8, 2026
Closed
ldayton#149 landed word_has_expansions (per-token: was the word built from a bash expansion), which already does what this PR's opaque_positions needed and a bit more — it also flags multi-expansion words like a$X$Y, and it's aligned to the handler's tokens through env prefixes and wrapper recursion. Resolve the conflict by dropping opaque_positions and pointing the kubectl secret-exposure checks at word_has_expansions, so there's a single expansion-tracking mechanism in the analyzer's security path instead of two parallel ones. Behavior is equivalent-or-stricter; the kubectl tests are unchanged and still pass. Co-authored-by: Nick Davies <github@nicolasdavies.com.au>
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.
Secrets -o yaml and config --raw could be leaking secrets that should be generally sealed in the cluster so don't allow those by default.
This also rethinks how sometimes-safe commands are treated: commands with opaque tokens (command substitutions, parameter expansions, indirect expansions) that could alter security-sensitive arguments are conservatively blocked. Handlers receive opaque_positions so they can detect when runtime-determined values bypass static checks.
I believe this is a sane pattern for handling this case. I did the same choice in the modules and -c PRs where if there are expansions we just default to unsafe. I think this is scoped down correctly though so that most
getcommands for kubectl (except forsecretare going to be approved automatically still the false-negative should be low