Alerts This Week
Warning Icon 1 714
Alerts This Week
Warning Icon 1 714

Gentoo: GLSA-201206-07 Normal: nginx Code Execution Risk

gentoo
Calendar Grey June 21, 2012
Dist Gentoo Esm H88
A security vulnerability in Apache may allow unauthorized access to sensitive data. Keep an eye out for patches and safety protocols.
A buffer overflow vulnerability in nginx could result in the execution of arbitrary code.

Summary

An error in ngx_http_mp4_module.c could cause a buffer overflow. NOTE: nginx must have been emerged with USE="nginx_modules_http_mp4" in order to be affected by this vulnerability.

Resolution

All nginx users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=www-servers/nginx-1.0.15"

References

[ 1 ] CVE-2012-2089 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-2089

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201206-07
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: nginx: User-assisted execution of arbitrary code
Date: June 21, 2012
Bugs: #411751
ID: 201206-07

Synopsis

A buffer overflow vulnerability in nginx could result in the execution of arbitrary code.

Background

nginx is a robust, small, and high performance HTTP and reverse proxy server.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 www-servers/nginx < 1.0.15 >= 1.0.15

Impact

===== A remote attacker could entice a user to place a specially crafted MP4 file on the nginx server, possibly resulting in execution of arbitrary code with the privileges of the process or a Denial of Service condition.

Workaround

There is no known workaround at this time.

Your message here