[AMBARI-23064] Upgrading jackson-databind (plus jackson-annotations and jackson-core) to 2.9.4 due to security concerns #453
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.
What changes were proposed in this pull request?
Per CVE-2018-5968
FasterXML jackson-databind through 2.8.11 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 and CVE-2017-17485 deserialization flaws. This is exploitable via two different gadgets that bypass a blacklist.How was this patch tested?
After updating the affected pom.xml files I've done the following:
1.) Checking Maven's dependency resolution:
2.) I executed
mvn clean installinutilityand inambari-server:3.) In addition to this; I replaced the content of
usr/lib/ambari-serverin my vagrant host with the content fromambari-server/target/ambari-server-2.6.0.0.0-dist/usr/lib/ambari-server(where the affected JAR were replaced with version 2.9.4) and restarted the server; logged in and did some actions (in this case I created a cluster); there were no any issues.