Validate Watcher Proxy Allowlist#144759
Conversation
|
Pinging @elastic/es-distributed (Team:Distributed) |
|
Hi @jfreden, I've created a changelog YAML for you. |
| } | ||
|
|
||
| RequestConfig.Builder config = RequestConfig.custom(); | ||
| validateProxyAgainstWhitelist(request.proxy); |
There was a problem hiding this comment.
Slightly worried about BWC here since it's been around for a while.
There was a problem hiding this comment.
Agreed. This could be an unwelcome surprise for users with a watcher proxy config not covered by the allowlist.
You might consider targeting the next minor version only rather than patch versions. But that leaves 8.19.x, 9.2.x, and 9.3.x systems vulnerable.
There was a problem hiding this comment.
Yes, it's a tricky tradeoff. After thinking some more about this I think targeting all branches makes the most sense. Here is my reasoning:
- The default is no allow list (anything is allowed), so users with the default won't be impacted (probably most users)
- If an explicit allow list is configured the user is worried about the vulnerability and want full protection, including checking the proxy host against the allow list.
- The allow list is almost useless without this fix and it's a bug.
WDYT?
There was a problem hiding this comment.
Agreed, that sounds reasonable to me.
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
* Validate Watcher Proxy Allowlist * Update docs/changelog/144759.yaml (cherry picked from commit 9b6d5a2)
* Validate Watcher Proxy Allowlist * Update docs/changelog/144759.yaml (cherry picked from commit 9b6d5a2)
* Validate Watcher Proxy Allowlist * Update docs/changelog/144759.yaml (cherry picked from commit 9b6d5a2)
* Validate Watcher Proxy Allowlist * Update docs/changelog/144759.yaml
Validates that a per-request proxy host is whitelisted. System-wide proxies configured via
xpack.http.proxy.hostare exempt.