Bump netty4 version from 4.1.34.Final to 4.1.50.Final - CVE-2019-16869 - CWE-113 #3006
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR bumps the version of Netty 4 dependencies to 4.1.50.Final
Related Issue
None
Description of the solution adopted
Bumper to the latest
4.1.x
version available.NO CQ needed while on the same patch release.
CQ for the 4.1.34.Final version here
Each single submodule of Netty 4 has been defined in the
dependencyManagement
of the rootpom.xml
so we can match any usages by other dependencies (i.e. Elasticsearch Transport).Below
mvn dependency:tree
command issued againstdevelop
and this branch.dependency tree - develop.txt
dependency tree - netty.txt
Screenshots
None
Any side note on the changes made
Netty 3 is still in use by
org.elasticsearch.plugin:transport-netty3-client
bu t is set on the latest version available. It will be removed when we will droptransport-netty3-client
usage.Branch is named
4.1.45.Final
because it was the latest available version at the I created the branch.