CVE Vulnerabilities

CVE-2018-5407

Exposure of Sensitive Information to an Unauthorized Actor

Published: Nov 15, 2018 | Modified: Nov 21, 2024
CVSS 3.x
4.7
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
1.9 LOW
AV:L/AC:M/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
4.8 MODERATE
CVSS:3.0/AV:P/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
Ubuntu
LOW

Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on port contention.

Weakness

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)
Ubuntu_linux Canonical 18.04 (including) 18.04 (including)
Ubuntu_linux Canonical 18.10 (including) 18.10 (including)
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-apr-0:1.6.3-63.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-apr-util-0:1.6.1-48.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-brotli-0:1.0.6-7.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-curl-0:7.64.1-14.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-httpd-0:2.4.37-33.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-jansson-0:2.11-20.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-mod_cluster-native-0:1.3.12-9.Final_redhat_2.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-mod_jk-0:1.2.46-22.redhat_1.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-mod_security-0:2.9.2-16.GA.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-nghttp2-0:1.39.2-4.jbcs.el6 *
JBoss Core Services on RHEL 6 RedHat jbcs-httpd24-openssl-1:1.1.1-25.jbcs.el6 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-apr-0:1.6.3-63.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-apr-util-0:1.6.1-48.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-brotli-0:1.0.6-7.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-curl-0:7.64.1-14.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-httpd-0:2.4.37-33.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-jansson-0:2.11-20.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-mod_cluster-native-0:1.3.12-9.Final_redhat_2.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-mod_jk-0:1.2.46-22.redhat_1.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-mod_security-0:2.9.2-16.GA.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-nghttp2-0:1.39.2-4.jbcs.el7 *
JBoss Core Services on RHEL 7 RedHat jbcs-httpd24-openssl-1:1.1.1-25.jbcs.el7 *
Red Hat Enterprise Linux 7 RedHat openssl-1:1.0.2k-16.el7_6.1 *
Red Hat Enterprise Linux 7 RedHat ovmf-0:20180508-6.gitee3198e672e2.el7 *
Red Hat JBoss Web Server 5 RedHat openssl *
Red Hat JBoss Web Server 5.2 on RHEL 6 RedHat jws5-ecj-0:4.12.0-1.redhat_1.1.el6jws *
Red Hat JBoss Web Server 5.2 on RHEL 6 RedHat jws5-javapackages-tools-0:3.4.1-5.15.11.el6jws *
Red Hat JBoss Web Server 5.2 on RHEL 6 RedHat jws5-jboss-logging-0:3.3.2-1.Final_redhat_00001.1.el6jws *
Red Hat JBoss Web Server 5.2 on RHEL 6 RedHat jws5-mod_cluster-0:1.4.1-1.Final_redhat_00001.2.el6jws *
Red Hat JBoss Web Server 5.2 on RHEL 6 RedHat jws5-tomcat-0:9.0.21-10.redhat_4.1.el6jws *
Red Hat JBoss Web Server 5.2 on RHEL 6 RedHat jws5-tomcat-native-0:1.2.21-34.redhat_34.el6jws *
Red Hat JBoss Web Server 5.2 on RHEL 6 RedHat jws5-tomcat-vault-0:1.1.8-1.Final_redhat_1.1.el6jws *
Red Hat JBoss Web Server 5.2 on RHEL 7 RedHat jws5-ecj-0:4.12.0-1.redhat_1.1.el7jws *
Red Hat JBoss Web Server 5.2 on RHEL 7 RedHat jws5-javapackages-tools-0:3.4.1-5.15.11.el7jws *
Red Hat JBoss Web Server 5.2 on RHEL 7 RedHat jws5-jboss-logging-0:3.3.2-1.Final_redhat_00001.1.el7jws *
Red Hat JBoss Web Server 5.2 on RHEL 7 RedHat jws5-mod_cluster-0:1.4.1-1.Final_redhat_00001.2.el7jws *
Red Hat JBoss Web Server 5.2 on RHEL 7 RedHat jws5-tomcat-0:9.0.21-10.redhat_4.1.el7jws *
Red Hat JBoss Web Server 5.2 on RHEL 7 RedHat jws5-tomcat-native-0:1.2.21-34.redhat_34.el7jws *
Red Hat JBoss Web Server 5.2 on RHEL 7 RedHat jws5-tomcat-vault-0:1.1.8-1.Final_redhat_1.1.el7jws *
Red Hat JBoss Web Server 5.2 on RHEL 8 RedHat jws5-ecj-0:4.12.0-1.redhat_1.1.el8jws *
Red Hat JBoss Web Server 5.2 on RHEL 8 RedHat jws5-javapackages-tools-0:3.4.1-5.15.11.el8jws *
Red Hat JBoss Web Server 5.2 on RHEL 8 RedHat jws5-jboss-logging-0:3.3.2-1.Final_redhat_00001.1.el8jws *
Red Hat JBoss Web Server 5.2 on RHEL 8 RedHat jws5-mod_cluster-0:1.4.1-1.Final_redhat_00001.2.el8jws *
Red Hat JBoss Web Server 5.2 on RHEL 8 RedHat jws5-tomcat-0:9.0.21-10.redhat_4.1.el8jws *
Red Hat JBoss Web Server 5.2 on RHEL 8 RedHat jws5-tomcat-native-0:1.2.21-34.redhat_34.el8jws *
Red Hat JBoss Web Server 5.2 on RHEL 8 RedHat jws5-tomcat-vault-0:1.1.8-1.Final_redhat_1.1.el8jws *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat imgbased-0:1.1.7-0.1.el7ev *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat ovirt-node-ng-0:4.3.0-0.20181213.0.el7ev *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat redhat-release-virtualization-host-0:4.3-0.5.el7 *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat redhat-virtualization-host-0:4.3-20190409.0.el7_6 *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat rhvm-appliance-0:4.3-20190409.0.el7 *
Text-Only JBCS RedHat openssl *
Openssl Ubuntu bionic *
Openssl Ubuntu precise/esm *
Openssl Ubuntu trusty *
Openssl Ubuntu upstream *
Openssl Ubuntu xenial *
Openssl098 Ubuntu trusty *
Openssl1.0 Ubuntu bionic *
Openssl1.0 Ubuntu cosmic *

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