- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202007-55
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: libetpan: Improper STARTTLS handling
     Date: July 28, 2020
     Bugs: #734130
       ID: 202007-55

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
=======
A vulnerability was discovered in libetpan's STARTTLS handling,
possibly allowing an integrity/confidentiality compromise.

Background
=========
libetpan is a portable, efficient middleware for different kinds of
mail access.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  net-libs/libetpan           < 1.9.4-r1               >= 1.9.4-r1

Description
==========
It was discovered that libetpan was not properly handling state within
the STARTTLS protocol handshake.

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

Workaround
=========
There is no known workaround at this time.

Resolution
=========
All libetpan users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-libs/libetpan-1.9.4-r1"

References
=========
[ 1 ] CVE-2020-15953
      https://nvd.nist.gov/vuln/detail/CVE-2020-15953

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202007-55

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.

License
======
Copyright 2020 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-202007-55: libetpan: Improper STARTTLS handling

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

Summary

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

Resolution

All libetpan users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=net-libs/libetpan-1.9.4-r1"

References


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

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202007-55

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
Severity: Normal
Title: libetpan: Improper STARTTLS handling
Date: July 28, 2020
Bugs: #734130
ID: 202007-55

Synopsis

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

Background

libetpan is a portable, efficient middleware for different kinds of mail access.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-libs/libetpan < 1.9.4-r1 >= 1.9.4-r1

Impact

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

Workaround

There is no known workaround at this time.

Related News