Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
1–10 of 32 posts
Re: Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
#2Re: Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
#3Re: Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
#4I wonder if this discovery is a result of OpenBSD switching its focus from Apache to Nginx ?
> Thanks to Lucas Molas, researcher at Programa STIC, Fundación Dr. Manuel Sadosky, Buenos Aires, Argentina.
Re: Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
#5Patch is pretty interesting. Why was buffer overflow protection behind a debug flag? http://nginx.org/download/patch.2014.spdy2.txt
Once that is done it's incredibly easy for these kind of bugs to go un-noticed for a long time.
Re: Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
#6Re: Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
#7I assume this only affects configurations with ngx_http_spdy_module enabled. Can anyone confirm whether or not that's the case?
The problem affects nginx 1.3.15 - 1.5.11, compiled with the ngx_http_spdy_module module (which is not compiled by default) and without --with-debug configure option, if the "spdy" option of the "listen" directive is used in a configuration file.
Re: Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
#8Patch is pretty interesting. Why was buffer overflow protection behind a debug flag? http://nginx.org/download/patch.2014.spdy2.txt
Re: Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
#9So for those who are using legacy version are they going to rely on distro vendor to push the patch? Just curious, even though I guess the number of users who have activated this experimental SPDY is low and people who actually have it enabled probably know how to fix it themselves.
Re: Nginx SPDY heap buffer overflow (affects 1.3.15 – 1.5.11)
#10Patch is pretty interesting. Why was buffer overflow protection behind a debug flag? http://nginx.org/download/patch.2014.spdy2.txt
Usual reason for mistakes like this is: someone was debugging something then (partially) forgot to clean up before committing. Once that is done it's incredibly easy for these kind of bugs to go un-noticed for a long time.