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
bug: cve exploiting malicious connection header #189
Conversation
7df5f5f
to
5af031a
Compare
5af031a
to
cfce8be
Compare
@prometherion it would be great if a GHSA could be created once this fix is released. |
553af54
to
6b0536d
Compare
6b0536d
to
440944a
Compare
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.
lgtm thanks for the nice work
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.
Lgtm!
func (n *kubeFilter) removingHopByHopHeaders(request *http.Request) { | ||
connectionHeaderName, upgradeHeaderName, requestUpgradeType := "connection", "upgrade", "" | ||
|
||
if httpguts.HeaderValuesContainsToken(request.Header[connectionHeaderName], upgradeHeaderName) { |
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.
request.Header[connectionHeaderName]
is incorrect due to casing of connectionHeaderName
.
Closes #188.
We strongly suggest upgrading ASAP
capsule-proxy
to mitigate this CVE that doesn't have direct mitigation.