Skip to content
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

Backport of Calculate namespace prefix before tainting route entries into release/1.14.x #21485

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #21470 to be assessed for backporting due to the inclusion of the label backport/1.14.x.

The below text is copied from the body of the original PR.


This is essentially the 'fix' code we used as part of resolving a recent sev 1, where we pre-calculate the namespace path, as we do in the other place we call c.router.Taint(ctx, path). The PR for that change is here: #15067 . I added debug logging including the places where we disagree, and added it to the other place we pre-calculate namespace prefixes.

There may be more adjustments/improvements we want to make to add additional safety to tainting, such as preventing the root "sys/" from ever being tainted, but if we did want to add those, we can do as part of a different PR. I wanted to keep this PR with a small scope, specifically targeting the fix.


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/violethynes/fix-taint-namespace-prefixes/correctly-immune-goshawk branch 2 times, most recently from 0b11675 to 5d0ea33 Compare June 27, 2023 19:10
@VioletHynes VioletHynes added this to the 1.14.1 milestone Jun 27, 2023
@VioletHynes VioletHynes enabled auto-merge (squash) June 27, 2023 19:12
@VioletHynes VioletHynes merged commit 927a827 into release/1.14.x Jun 27, 2023
83 checks passed
@VioletHynes VioletHynes deleted the backport/violethynes/fix-taint-namespace-prefixes/correctly-immune-goshawk branch June 27, 2023 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants