REDHAT-BUG-803856: Medium severity nginx vulnerability
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] http://seclists.org/bugtraq/2012/Mar/65 [2] http://trac.nginx.org/nginx/changeset/4530/nginx [3] http://trac.nginx.org/nginx/changeset/4531/nginx [4] http://nginx.org/download/patch.2012.memory.txt
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-803856?
The severity of REDHAT-BUG-803856 is considered high due to potential leakage of sensitive information.
How do I fix REDHAT-BUG-803856?
To fix REDHAT-BUG-803856, upgrade Nginx to version 1.0.14 or 1.1.17 or later.
What versions of Nginx are affected by REDHAT-BUG-803856?
Nginx versions prior to 1.0.14 and 1.1.17 are affected by REDHAT-BUG-803856.
What type of information could be leaked due to REDHAT-BUG-803856?
REDAHT-BUG-803856 could leak sensitive content from previously freed memory to the HTTP client.
Is REDHAT-BUG-803856 a remote vulnerability?
Yes, REDHAT-BUG-803856 can be exploited remotely when the server responds to an HTTP request.