Alerts This Week
Warning Icon 1 764
Alerts This Week
Warning Icon 1 764

Gentoo: GLSA-201502-06 Normal: nginx SSL Session Fixation

gentoo
Calendar Grey February 7, 2015
Dist Gentoo Esm H88
Cybercriminals could take advantage of nginx SSL session fixation vulnerabilities to gain access to confidential data. It is advisable to perform an upgrade.
An SSL session fixation vulnerability in nginx may allow remote attackers to obtain sensitive information.

Summary

An SSL session fixation vulnerability has been found in nginx when multiple servers use the same shared ssl_session_cache or ssl_session_ticket_key.

Resolution

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

References

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

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201502-06
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: Information disclosure
Date: February 07, 2015
Bugs: #522994
ID: 201502-06

Synopsis

An SSL session fixation vulnerability in nginx may allow remote attackers to obtain sensitive information.

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.7.6 >= 1.7.6

Impact

===== A remote attacker may be able to obtain sensitive information.

Workaround

There is no known workaround at this time.

Your message here