Lucene search

K
ibmIBM2EE525D2EA98139EECBD98B625477DDDD5A658E5F81D79BC18E2A76F2D1FAAC6
HistoryFeb 05, 2020 - 12:53 a.m.

Security Bulletin: Multiple Security Vulnerabilities in OpenSSL Affect IBM Sterling B2B Integrator (CVE-2018-0734, CVE-2018-5407)

2020-02-0500:53:36
www.ibm.com
17

EPSS

0.003

Percentile

71.6%

Summary

Security vulnerabilities in OpenSSL affect IBM Sterling B2B Integrator

Vulnerability Details

CVE-ID: CVE-2018-0734
Description: OpenSSL could allow a remote attacker to obtain sensitive information, caused by a timing side channel attack in the DSA signature algorithm. An attacker could exploit this vulnerability using variations in the signing algorithm to recover the private key.
CVSS Base Score: 3.7
CVSS Temporal Score: <https://exchange.xforce.ibmcloud.com/vulnerabilities/152085&gt; for more information
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)

CVEID: CVE-2018-5407 DESCRIPTION: Multiple SMT/Hyper-Threading architectures and processors could allow a local attacker to obtain sensitive information, caused by execution engine sharing on Simultaneous Multithreading (SMT) architecture. By using the PortSmash new side-channel attack, an attacker could run a malicious process next to legitimate processes using the architectures parallel thread running capabilities to leak encrypted data from the CPU’s internal processes. Note: This vulnerability is known as PortSmash.
CVSS Base Score: 5.1
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/152484&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)

Affected Products and Versions

IBM Sterling B2B Integrator 5.2.0.1 - 6.0.0.0

Remediation/Fixes

PRODUCT & Version

|

Remediation/Fix

—|—

IBM Sterling B2B Integrator 5.2.0.1 - 6.0.0.0

|

SWIFTNet Customers must upgrade their B2B Integrator at least to 5020603_2, 5020602_4 , 5020601_7 or 6.0.0.0 available on Fix Central and current version of OpenSSL to version 1.0.2q

Workarounds and Mitigations

No