You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
here is a bug, if we make a http request with more than 64 http headers, then varnish will issue a 413 error, and this will go on to call vcl_error, however, vcl_error may already be hooked by lib-parsereq, thus the hooked error function will be called. The hooked error function will try to initialise the module and do http_SetHeader. Here is the problem, the call to http_SetHeader will fail because there are already 64 headers, so parsereq-mod will keep trying to reinitialise itself and exhaust the stack, finally core dumped.
The text was updated successfully, but these errors were encountered:
I am afraid that the new version still have this flaw, because a malformed request with more than 64 http request header can still prevent a new header (which we use in libvmod-parsereq) from being set, thus coredump
here is a bug, if we make a http request with more than 64 http headers, then varnish will issue a 413 error, and this will go on to call vcl_error, however, vcl_error may already be hooked by lib-parsereq, thus the hooked error function will be called. The hooked error function will try to initialise the module and do http_SetHeader. Here is the problem, the call to http_SetHeader will fail because there are already 64 headers, so parsereq-mod will keep trying to reinitialise itself and exhaust the stack, finally core dumped.
The text was updated successfully, but these errors were encountered: