CVE-2018-5407 : Detail

CVE-2018-5407

4.7
/
Medium
A01-Broken Access Control
0.07%V3
Local
2018-11-15
20h00 +00:00
2020-04-15
19h06 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

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'.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-203 Observable Discrepancy
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 4.7 MEDIUM CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

High

successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 [email protected]
V2 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Exploit information

Exploit Database EDB-ID : 45785

Publication date : 2018-11-01 23h00 +00:00
Author : Billy Brumley
EDB Verified : No

# Summary This is a proof-of-concept exploit of the PortSmash microarchitecture attack, tracked by CVE-2018-5407. ![Alt text](parse_raw_simple.png?raw=true "Title") # Setup ## Prerequisites A CPU featuring SMT (e.g. Hyper-Threading) is the only requirement. This exploit code should work out of the box on Skylake and Kaby Lake. For other SMT architectures, customizing the strategies and/or waiting times in `spy` is likely needed. ## OpenSSL Download and install OpenSSL 1.1.0h or lower: cd /usr/local/src wget https://www.openssl.org/source/openssl-1.1.0h.tar.gz tar xzf openssl-1.1.0h.tar.gz cd openssl-1.1.0h/ export OPENSSL_ROOT_DIR=/usr/local/ssl ./config -d shared --prefix=$OPENSSL_ROOT_DIR --openssldir=$OPENSSL_ROOT_DIR -Wl,-rpath=$OPENSSL_ROOT_DIR/lib make -j8 make test sudo checkinstall --strip=no --stripso=no --pkgname=openssl-1.1.0h-debug --provides=openssl-1.1.0h-debug --default make install_sw If you use a different path, you'll need to make changes to `Makefile` and `sync.sh`. # Tooling ## freq.sh Turns off frequency scaling and TurboBoost. ## sync.sh Sync trace through pipes. It has two victims, one of which should be active at a time: 1. The stock `openssl` running `dgst` command to produce a P-384 signature. 2. A harness `ecc` that calls scalar multiplication directly with a known key. (Useful for profiling.) The script will generate a P-384 key pair in `secp384r1.pem` if it does not already exist. The script outputs `data.bin` which is what `openssl dgst` signed, and you should be able to verify the ECDSA signature `data.sig` afterwards with openssl dgst -sha512 -verify secp384r1.pem -signature data.sig data.bin In the `ecc` tool case, `data.bin` and `secp384r1.pem` are meaningless and `data.sig` is not created. For the `taskset` commands in `sync.sh`, the cores need to be two logical cores of the same physical core; sanity check with $ grep '^core id' /proc/cpuinfo core id : 0 core id : 1 core id : 2 core id : 3 core id : 0 core id : 1 core id : 2 core id : 3 So the script is currently configured for logical cores 3 and 7 that both map to physical core 3 (`core_id`). ## spy Measurement process that outputs measurements in `timings.bin`. To change the `spy` strategy, check the port defines in `spy.h`. Only one strategy should be active at build time. Note that `timings.bin` is actually raw clock cycle counter values, not latencies. Look in `parse_raw_simple.py` to understand the data format if necessary. ## ecc Victim harness for running OpenSSL scalar multiplication with known inputs. Example: ./ecc M 4 deadbeef0123456789abcdef00000000c0ff33 Will execute 4 consecutive calls to `EC_POINT_mul` with the given hex scalar. ## parse_raw_simple.py Quick and dirty hack to view 1D traces. The top plot is the raw trace. Everything below is a different digital filter of the raw trace for viewing purposes. Zoom and pan are your friends here. You might have to adjust the `CEIL` variable if the plots are too aggressively clipped. Python packages: sudo apt-get install python-numpy python-matplotlib # Usage Turn off frequency scaling: ./freq.sh Make sure everything builds: make clean make Take a measurement: ./sync.sh View the trace: python parse_raw_simple.py timings.bin You can play around with one victim at a time in `sync.sh`. Sample output for the `openssl dgst` victim is in `parse_raw_simple.png`. # Credits * Alejandro Cabrera Aldaya (Universidad Tecnológica de la Habana (CUJAE), Habana, Cuba) * Billy Bob Brumley (Tampere University of Technology, Tampere, Finland) * Sohaib ul Hassan (Tampere University of Technology, Tampere, Finland) * Cesar Pereida García (Tampere University of Technology, Tampere, Finland) * Nicola Tuveri (Tampere University of Technology, Tampere, Finland) EDB Download: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/45785.zip

Products Mentioned

Configuraton 0

Canonical>>Ubuntu_linux >> Version 14.04

Canonical>>Ubuntu_linux >> Version 16.04

Canonical>>Ubuntu_linux >> Version 18.04

Canonical>>Ubuntu_linux >> Version 18.10

Configuraton 0

Debian>>Debian_linux >> Version 8.0

Debian>>Debian_linux >> Version 9.0

Configuraton 0

Nodejs>>Node.js >> Version To (excluding) 6.14.4

Nodejs>>Node.js >> Version From (including) 8.0.0 To (excluding) 8.11.4

Nodejs>>Node.js >> Version From (including) 10.0.0 To (excluding) 10.9.0

Configuraton 0

Openssl>>Openssl >> Version From (including) 1.0.2 To (excluding) 1.0.2q

Openssl>>Openssl >> Version From (including) 1.1.0 To (excluding) 1.1.0i

Configuraton 0

Tenable>>Nessus >> Version To (excluding) 8.1.1

Configuraton 0

Oracle>>Api_gateway >> Version 11.1.2.4.0

Oracle>>Application_server >> Version 0.9.8

Oracle>>Application_server >> Version 1.0.0

Oracle>>Application_server >> Version 1.0.1

Oracle>>Enterprise_manager_base_platform >> Version 12.1.0.5.0

Oracle>>Enterprise_manager_base_platform >> Version 13.2.0.0.0

Oracle>>Enterprise_manager_base_platform >> Version 13.3.0.0.0

Oracle>>Enterprise_manager_ops_center >> Version 12.3.3

Oracle>>Mysql_enterprise_backup >> Version To (including) 3.12.3

Oracle>>Mysql_enterprise_backup >> Version From (including) 3.12.4 To (including) 4.1.2

Oracle>>Peoplesoft_enterprise_peopletools >> Version 8.55

Oracle>>Peoplesoft_enterprise_peopletools >> Version 8.56

Oracle>>Peoplesoft_enterprise_peopletools >> Version 8.57

Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version From (including) 17.7 To (including) 17.12

  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 17.7 (Open CPE detail)
  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 17.8 (Open CPE detail)
  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 17.9 (Open CPE detail)
  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 17.10 (Open CPE detail)
  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 17.11 (Open CPE detail)
  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 17.12 (Open CPE detail)

Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 8.4

  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 8.4 (Open CPE detail)

Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 15.1

  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 15.1 (Open CPE detail)

Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 15.2

  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 15.2 (Open CPE detail)

Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 16.1

  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 16.1 (Open CPE detail)

Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 16.2

  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 16.2 (Open CPE detail)

Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 18.8

  • Oracle>>Primavera_p6_enterprise_project_portfolio_management >> Version 18.8 (Open CPE detail)

Oracle>>Tuxedo >> Version 12.1.1.0.0

Oracle>>Vm_virtualbox >> Version To (excluding) 6.0.0

Configuraton 0

Redhat>>Enterprise_linux_desktop >> Version 7.0

Redhat>>Enterprise_linux_server >> Version 7.0

Redhat>>Enterprise_linux_server >> Version 7.6

Redhat>>Enterprise_linux_server_aus >> Version 7.6

Redhat>>Enterprise_linux_server_eus >> Version 7.6

Redhat>>Enterprise_linux_server_tus >> Version 7.6

Redhat>>Enterprise_linux_workstation >> Version 7.0

References

https://access.redhat.com/errata/RHSA-2019:0483
Tags : vendor-advisory, x_refsource_REDHAT
https://usn.ubuntu.com/3840-1/
Tags : vendor-advisory, x_refsource_UBUNTU
https://www.debian.org/security/2018/dsa-4355
Tags : vendor-advisory, x_refsource_DEBIAN
https://security.gentoo.org/glsa/201903-10
Tags : vendor-advisory, x_refsource_GENTOO
https://www.exploit-db.com/exploits/45785/
Tags : exploit, x_refsource_EXPLOIT-DB
https://www.debian.org/security/2018/dsa-4348
Tags : vendor-advisory, x_refsource_DEBIAN
http://www.securityfocus.com/bid/105897
Tags : vdb-entry, x_refsource_BID
https://access.redhat.com/errata/RHSA-2019:0651
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2019:0652
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2019:2125
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2019:3929
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2019:3933
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2019:3931
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2019:3935
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2019:3932
Tags : vendor-advisory, x_refsource_REDHAT