Bug 1835363 (CVE-2020-11050)

Summary: CVE-2020-11050 java-websocket: WebSocketClient does not perform SSL hostname validation
Product: [Other] Security Response Reporter: Guilherme de Almeida Suckevicz <gsuckevi>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: aileenc, bibryam, chazlett, drieden, ganandan, ggaughan, gmalinko, hbraun, janstey, jochrist, jwon, pantinor
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-01 13:01:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1916883    

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