SB2018071925 - Multiple vulnerabilities in IBM Flex System EN6131 40Gb Ethernet / IB6131 40Gb Infiniband Switch Firmware



SB2018071925 - Multiple vulnerabilities in IBM Flex System EN6131 40Gb Ethernet / IB6131 40Gb Infiniband Switch Firmware

Published: July 19, 2018 Updated: February 11, 2026

Security Bulletin ID SB2018071925
CSH Severity
Medium
Patch available
YES
Number of vulnerabilities 3
Exploitation vector Remote access
Highest impact Information disclosure

Breakdown by Severity

Medium 67% Low 33%
  • Low
  • Medium
  • High
  • Critical

Description

This security bulletin contains information about 3 vulnerabilities.


1) Open redirect (CVE-ID: CVE-2017-1000100)

The vulnerability allows a remote attacker to redirect website visitors to external websites.

The weakness exists due to incorrect validation of redirected URL. A remote attacker can redirect the target user's curl request to a TFTP URL with a long filename to cause the target user's curl application to send portions of system memory.

Successful exploitation of the vulnerability results in information disclosure.

2) Cryptographic issues (CVE-ID: CVE-2016-5419)

The vulnerability allows a remote non-authenticated attacker to gain access to sensitive information.

curl and libcurl before 7.50.1 do not prevent TLS session resumption when the client certificate has changed, which allows remote attackers to bypass intended restrictions by resuming a session.


3) Improper Authorization (CVE-ID: CVE-2016-5420)

The vulnerability allows a remote attacker to gain access to sensitive information.

The vulnerability exists due to an error when handling client TLS certificates during connection reuse. libcurl supports reuse of established connections for subsequent requests. It does this by keeping a few previous connections "alive" in a connection pool so that a subsequent request that can use one of them instead of creating a new connection will do so.

When using a client certificate for a connection that was then put into the connection pool, that connection could then wrongly get reused in a subsequent request to that same server that either didn't use a client certificate at all or that asked to use a different client certificate thus trying to tell the user that it is a different entity.

This mistakenly using the wrong connection could of course lead to applications sending requests to the wrong realms of the server using authentication that it wasn't supposed to have for those operations.


Remediation

Install update from vendor's website.