Bug 1835363 (CVE-2020-11050) - CVE-2020-11050 java-websocket: WebSocketClient does not perform SSL hostname validation
Summary: CVE-2020-11050 java-websocket: WebSocketClient does not perform SSL hostname ...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2020-11050
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1916883
TreeView+ depends on / blocked
 
Reported: 2020-05-13 16:56 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-03-01 13:01 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-03-01 13:01:55 UTC
Embargoed:

Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-05-13 16:56:29 UTC 
In Java-WebSocket less than or equal to 1.4.1, there is an Improper Validation of Certificate with Host Mismatch where WebSocketClient does not perform SSL hostname validation. This has been patched in 1.5.0.

Reference:
https://github.com/TooTallNate/Java-WebSocket/security/advisories/GHSA-gw55-jm4h-x339
Comment 1 Jonathan Christison 2021-03-01 11:20:09 UTC 
Marking Red Hat Fuse 7 and Red Hat Integration Camel K as being not affected, this is because although java-websocket artifacts are pulled in at build time (org.java-websocket:Java-WebSocket) for the camel-web3j component, The websocket functionality is not used, Camel uses `org.web3j.protocol.Web3jService` which is the default interface to interact with the JSON-RPC API in web3j, there is no use of `WebSocketService` or `WebSocketClient` which is a alternate transport in web3j that makes use of org.java-websocket:Java-WebSocket.
Comment 3 Product Security DevOps Team 2021-03-01 13:01:55 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2020-11050
Note You need to log in before you can comment on or make changes to this bug.