CVE Vulnerabilities

CVE-2018-1059

Exposure of Sensitive Information to an Unauthorized Actor

Published: Apr 24, 2018 | Modified: Nov 21, 2024
CVSS 3.x
6.1
MEDIUM
Source:
NVD
CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
CVSS 2.x
2.9 LOW
AV:A/AC:M/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
6.1 MODERATE
CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
Ubuntu
LOW
root.io logo minimus.io logo echo.ai logo

The DPDK vhost-user interface does not check to verify that all the requested guest physical range is mapped and contiguous when performing Guest Physical Addresses to Host Virtual Addresses translations. This may lead to a malicious guest exposing vhost-user backend process memory. All versions before 18.02.1 are vulnerable.

Weakness

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

Affected Software

NameVendorStart VersionEnd Version
Ubuntu_linuxCanonical17.10 (including)17.10 (including)
Ubuntu_linuxCanonical18.04 (including)18.04 (including)
Fast Datapath for Red Hat Enterprise Linux 7RedHatopenvswitch-0:2.9.0-19.el7fdp*
Red Hat Enterprise Linux 7 ExtrasRedHatdpdk-0:17.11-11.el7*
Red Hat OpenStack Platform 10.0 (Newton)RedHatopenstack-selinux-0:0.8.14-5.el7ost*
Red Hat OpenStack Platform 10.0 (Newton)RedHatopenvswitch-0:2.9.0-19.el7fdp.1*
Red Hat OpenStack Platform 12.0 (Pike)RedHatopenvswitch-0:2.9.0-19.el7fdp.1*
Red Hat Virtualization 4.2 for Red Hat Enterprise Linux 7.6 EUSRedHatopenvswitch-0:2.9.0-19.el7fdp*
Red Hat Virtualization Engine 4.2RedHatopenvswitch-0:2.9.0-19.el7fdp*
DpdkUbuntuartful*
DpdkUbuntubionic*
DpdkUbuntucosmic*
DpdkUbuntudevel*
DpdkUbuntudisco*
DpdkUbuntueoan*
DpdkUbuntuesm-infra/bionic*
DpdkUbuntuesm-infra/focal*
DpdkUbuntuesm-infra/xenial*
DpdkUbuntufocal*
DpdkUbuntugroovy*
DpdkUbuntuhirsute*
DpdkUbuntuimpish*
DpdkUbuntujammy*
DpdkUbuntukinetic*
DpdkUbuntulunar*
DpdkUbuntumantic*
DpdkUbuntunoble*
DpdkUbuntuoracular*
DpdkUbuntuplucky*
DpdkUbuntuquesting*
DpdkUbuntuupstream*
DpdkUbuntuxenial*

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.

References