Alerts This Week
Warning Icon 1 727
Alerts This Week
Warning Icon 1 727

Gentoo: GLSA-202006-01 Normal: GnuTLS Information Disclosure Risk

gentoo
Calendar Grey June 9, 2020
Dist Gentoo Esm H88
Disclosure of confidential information via GnuTLS security flaw. Urgent upgrade advised to avert remote exploitation.
An information disclosure vulnerability in GnuTLS allow remote attackers to obtain sensitive information.

Summary

A flaw was reported in the TLS session ticket key construction in GnuTLS.

Resolution

All GnuTLS user should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=net-libs/gnutls-3.6.14"

References

[ 1 ] CVE-2020-13777 https://nvd.nist.gov/vuln/detail/CVE-2020-13777

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202006-01
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: GnuTLS: Information disclosure
Date: June 09, 2020
Bugs: #727108
ID: 202006-01

Synopsis

An information disclosure vulnerability in GnuTLS allow remote attackers to obtain sensitive information.

Background

GnuTLS is an Open Source implementation of the TLS and SSL protocols.

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 net-libs/gnutls < 3.6.14 >= 3.6.14

Impact

===== A remote attacker could recover previous conversations in TLS 1.2 and obtain sensitive information or conduct a man-in-the-middle attack to bypass authentication in TLS 1.3.

Workaround

There is no known workaround at this time.

Your message here