CVE Vulnerabilities


Exposure of Sensitive Information to an Unauthorized Actor

Published: Jul 20, 2018 | Modified: Sep 18, 2018
CVSS 3.x
CVSS 2.x

camel/providers/imapx/camel-imapx-server.c in the IMAPx component in GNOME evolution-data-server before 3.21.2 proceeds with cleartext data containing a password if the client wishes to use STARTTLS but the server will not use STARTTLS, which makes it easier for remote attackers to obtain sensitive information by sniffing the network. The server code was intended to report an error and not proceed, but the code was written incorrectly.


The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Ubuntu_linux Canonical 14.04 (including) 14.04 (including)
Ubuntu_linux Canonical 16.04 (including) 16.04 (including)
Red Hat Enterprise Linux 7 RedHat evolution-data-server-0:3.12.11-37.el7 *
Red Hat Enterprise Linux 7 RedHat evolution-ews-0:3.12.11-9.el7 *
Red Hat Enterprise Linux 7 RedHat evolution-mapi-0:3.12.10-5.el7 *
Red Hat Enterprise Linux 7 RedHat openchange-0:2.3-2.el7 *
Evolution-data-server Ubuntu esm-infra/xenial *
Evolution-data-server Ubuntu trusty *
Evolution-data-server Ubuntu upstream *
Evolution-data-server Ubuntu xenial *

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.