-
Notifications
You must be signed in to change notification settings - Fork 5.2k
ext_proc: re-enable sending local replies to the ext_proc server #41769
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
Conversation
Signed-off-by: Yanjun Xiang <[email protected]>
|
/assign @yanavlasov @tyxia |
|
/retest |
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!
@yanjunxiang-google could you please add some context in pr description, so that people can track it easily
I think we can re-enable it is because CVE #38818 has been fixed. I don't remember which PR # fix ext_proc+web_socket
Yeah, for CVE #38818, we made two changes, one in ext_proc to disable local reply sending to the ext_proc server. The other is in router.h which is to cleanup some dangling pointer. Looking back, the change in ext_proc avoided the crash in some specific case, but not fixing the root cause. The change in router.h fixed the root cause. As there are some ext_proc users are asking for having local replies be sent to the ext_proc server, let's revert the ext_proc changes there. |
Yea, i meant could you reference the PR that fix the issue in router.h? Thanks |
Local replies generated from upstream filter chain should be able to sent to the ext_proc server.