Skip to content

Backport of VAULT-6803: fix listener issue if using proxy_protocol_behavior with deny_unauthorized for untrusted upstream connections into release/1.17.x#27608

Merged
peteski22 merged 2 commits intorelease/1.17.xfrom
backport/peteski22/VAULT-6803/listener-proxy-behavior-bug-allow-deny/adversely-growing-insect
Jun 26, 2024
Merged

Backport of VAULT-6803: fix listener issue if using proxy_protocol_behavior with deny_unauthorized for untrusted upstream connections into release/1.17.x#27608
peteski22 merged 2 commits intorelease/1.17.xfrom
backport/peteski22/VAULT-6803/listener-proxy-behavior-bug-allow-deny/adversely-growing-insect

Conversation

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

Backport

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

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


Description

This PR corrects an issue introduced when supported was added for PROXY v2 on TCP listeners using proxy_protocol_behavior.

This issue was introduced in Vault v1.10.0 and has impacted all subsequent versions other than v1.16.x (due to a bug parsing this config setting).

Any listener configured to deny_unauthorized will still close a connection when the upstream proxy is untrusted, but it will now continue to listen for connections until a valid one is found. It does this by returning ErrInvalidUpstream to the proxy library.

NOTE: the issue is only present if this config setting proxy_protocol_behavior is enabled and set to deny_unauthorized.

HashiCorp checklist

  • Labels: If this PR is the CE portion of an ENT change, and that ENT change is
    getting backported to N-2, use the new style backport/ent/x.x.x+ent labels
    instead of the old style backport/x.x.x labels.
  • Labels: If this PR is a CE only change, it can only be backported to N, so use
    the normal backport/x.x.x label (there should be only 1).
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/peteski22/VAULT-6803/listener-proxy-behavior-bug-allow-deny/adversely-growing-insect branch from 5f44de7 to a4a1a8e Compare June 26, 2024 07:52
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jun 26, 2024
@github-actions
Copy link

github-actions bot commented Jun 26, 2024

CI Results:
All Go tests succeeded! ✅

@github-actions
Copy link

Build Results:
All builds succeeded! ✅

@peteski22 peteski22 merged commit 67adf3e into release/1.17.x Jun 26, 2024
@peteski22 peteski22 deleted the backport/peteski22/VAULT-6803/listener-proxy-behavior-bug-allow-deny/adversely-growing-insect branch June 26, 2024 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-milestone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants