First published: Thu Mar 15 2012(Updated: )
A flaw was reported [1] in nginx versions prior to 1.0.14 and 1.1.17 where contents of previously freed memory could be sent to a client if an upstream server returned a specially crafted HTTP response. This could potentially leak sensitive information to the HTTP client. This has been corrected upstream [2],[3] and a patch [4] is available for earlier versions of nginx. [1] <a href="http://seclists.org/bugtraq/2012/Mar/65">http://seclists.org/bugtraq/2012/Mar/65</a> [2] <a href="http://trac.nginx.org/nginx/changeset/4530/nginx">http://trac.nginx.org/nginx/changeset/4530/nginx</a> [3] <a href="http://trac.nginx.org/nginx/changeset/4531/nginx">http://trac.nginx.org/nginx/changeset/4531/nginx</a> [4] <a href="http://nginx.org/download/patch.2012.memory.txt">http://nginx.org/download/patch.2012.memory.txt</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Nginx | <1.0.14<1.1.17 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-803856 is considered high due to potential leakage of sensitive information.
To fix REDHAT-BUG-803856, upgrade Nginx to version 1.0.14 or 1.1.17 or later.
Nginx versions prior to 1.0.14 and 1.1.17 are affected by REDHAT-BUG-803856.
REDAHT-BUG-803856 could leak sensitive content from previously freed memory to the HTTP client.
Yes, REDHAT-BUG-803856 can be exploited remotely when the server responds to an HTTP request.