Alerts This Week
Warning Icon 1 924
Alerts This Week
Warning Icon 1 924

Gentoo: GLSA 202007-56 Normal: Claws Mail STARTTLS Handling Threat

gentoo
Calendar Grey July 28, 2020
Dist Gentoo Esm H88
Gentoo Linux Security Advisory GLSA 202008-09 addresses a low severity vulnerability in the handling of STARTTLS by Claws Mail.
A vulnerability was discovered in Claws Mail's STARTTLS handling, possibly allowing an integrity/confidentiality compromise.

Summary

It was discovered that Claws Mail was not properly handling state within the STARTTLS protocol handshake.

Resolution

All Claws Mail users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=mail-client/claws-mail-3.17.6"

References

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

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202007-56
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: Claws Mail: Improper STARTTLS handling
Date: July 28, 2020
Bugs: #733684
ID: 202007-56

Synopsis

A vulnerability was discovered in Claws Mail's STARTTLS handling, possibly allowing an integrity/confidentiality compromise.

Background

Claws Mail is a GTK based e-mail client.

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 mail-client/claws-mail < 3.17.6 >= 3.17.6

Impact

===== There may be a breach of integrity or confidentiality in connections made using Claws Mail with STARTTLS.

Workaround

There is no known workaround at this time.

Your message here