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>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
F5 NGINX | >=0.1.0<1.0.14 | |
F5 NGINX | >=1.1.0<1.1.17 | |
Fedora | =15 | |
Fedora | =16 | |
Fedora | =17 | |
Debian | =6.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-1180 has a moderate severity rating due to potential information leakage.
To fix CVE-2012-1180, upgrade to nginx version 1.0.14 or 1.1.17 or later.
CVE-2012-1180 affects nginx versions prior to 1.0.14 and 1.1.17, along with certain Fedora and Debian releases.
The impact of CVE-2012-1180 is the potential leakage of sensitive information from previously freed memory.
As of the last reports, there is no evidence of CVE-2012-1180 being actively exploited in the wild.