[CVE-2020-36518] Update jackson-databind to 2.13.2.2

[reta]

Signed-off-by: Andriy Redko andriy.redko@aiven.io

Description

Update jackson-databind to 2.13.2.2
Blocked by FasterXML/jackson-databind#3428

Issues Resolved

Closes #2597

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[opensearch-ci-bot]

❌   Gradle Check failure a8db80b11cf901f4332e6f62157d7696b49346ef
Log 3762

Reports 3762

[opensearch-ci-bot]

❌   Gradle Check failure 541f4f90a1b1d2d0e5cb85051cd300eb36818e92
Log 3848

Reports 3848

[reta]

@dblock @andrross addressing CVE for Jackson, please take a look :) thanks!

[opensearch-ci-bot]

✅   Gradle Check success 4059045
Log 3850

Reports 3850

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-2599-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d8a1ba691204976e1b0e4ffc8e62b08a22e63692
# Push it to GitHub
git push --set-upstream origin backport/backport-2599-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-2599-to-2.x.

[opensearch-trigger-bot]

The backport to 1.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.3 1.3
# Navigate to the new working tree
cd .worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-2599-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d8a1ba691204976e1b0e4ffc8e62b08a22e63692
# Push it to GitHub
git push --set-upstream origin backport/backport-2599-to-1.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3

Then, create a pull request where the base branch is 1.3 and the compare/head branch is backport/backport-2599-to-1.3.

[opensearch-trigger-bot]

The backport to 1.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.x 1.x
# Navigate to the new working tree
cd .worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-2599-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d8a1ba691204976e1b0e4ffc8e62b08a22e63692
# Push it to GitHub
git push --set-upstream origin backport/backport-2599-to-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.x

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-2599-to-1.x.

[heatherdoone]

We upgraded to 2.13.2.2 and we are still seeing the StackOverflowError reported here: #2597

[reta]

We upgraded to 2.13.2.2 and we are still seeing the StackOverflowError reported here: #2597

thanks @heatherdoone , do you see it with OpenSearch or just confirming the bug is not fixed actually?

[heatherdoone]

I thought 2.13.2.2 already had the fix for the StackOverFlowError. Looks like it is getting merged soon? Or is the fix there now and we just need to pull it again?

[reta]

@heatherdoone according to FasterXML/jackson-databind#2816, it is fixed