[CVE-2023-2976] Fix google-java-format-1.17.0.jar: 1 vulnerabilities#526
Merged
lezzago merged 2 commits intoopensearch-project:mainfrom Aug 31, 2023
Merged
[CVE-2023-2976] Fix google-java-format-1.17.0.jar: 1 vulnerabilities#526lezzago merged 2 commits intoopensearch-project:mainfrom
lezzago merged 2 commits intoopensearch-project:mainfrom
Conversation
Signed-off-by: Sandesh Kumar <kusandes@amazon.com>
Codecov Report
@@ Coverage Diff @@
## main #526 +/- ##
=========================================
Coverage 28.20% 28.20%
Complexity 941 941
=========================================
Files 236 236
Lines 9864 9864
Branches 1118 1118
=========================================
Hits 2782 2782
Misses 6841 6841
Partials 241 241 |
eirsep
approved these changes
Aug 31, 2023
lezzago
approved these changes
Aug 31, 2023
opensearch-trigger-bot bot
pushed a commit
that referenced
this pull request
Aug 31, 2023
…526) * CVE-2023-2976 Fix google-java-format-1.17.0.jar: 1 vulnerabilities Signed-off-by: Sandesh Kumar <kusandes@amazon.com> * fix Signed-off-by: Sandesh Kumar <kusandes@amazon.com> --------- Signed-off-by: Sandesh Kumar <kusandes@amazon.com> Co-authored-by: Sandesh Kumar <kusandes@amazon.com> (cherry picked from commit 066eaee)
Contributor
|
The backport to 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.8 2.8
# Navigate to the new working tree
cd .worktrees/backport-2.8
# Create a new branch
git switch --create backport/backport-526-to-2.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 066eaeece19d68a9838af933533c4daf38e47fa1
# Push it to GitHub
git push --set-upstream origin backport/backport-526-to-2.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.8Then, create a pull request where the |
Contributor
|
The backport to 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.9 2.9
# Navigate to the new working tree
cd .worktrees/backport-2.9
# Create a new branch
git switch --create backport/backport-526-to-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 066eaeece19d68a9838af933533c4daf38e47fa1
# Push it to GitHub
git push --set-upstream origin backport/backport-526-to-2.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.9Then, create a pull request where the |
Contributor
|
The backport to 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.7 2.7
# Navigate to the new working tree
cd .worktrees/backport-2.7
# Create a new branch
git switch --create backport/backport-526-to-2.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 066eaeece19d68a9838af933533c4daf38e47fa1
# Push it to GitHub
git push --set-upstream origin backport/backport-526-to-2.7
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.7Then, create a pull request where the |
Contributor
|
The backport to 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.4 2.4
# Navigate to the new working tree
cd .worktrees/backport-2.4
# Create a new branch
git switch --create backport/backport-526-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 066eaeece19d68a9838af933533c4daf38e47fa1
# Push it to GitHub
git push --set-upstream origin backport/backport-526-to-2.4
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.4Then, create a pull request where the |
Contributor
|
The backport to 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.5 2.5
# Navigate to the new working tree
cd .worktrees/backport-2.5
# Create a new branch
git switch --create backport/backport-526-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 066eaeece19d68a9838af933533c4daf38e47fa1
# Push it to GitHub
git push --set-upstream origin backport/backport-526-to-2.5
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.5Then, create a pull request where the |
Contributor
|
The backport to 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.6 2.6
# Navigate to the new working tree
cd .worktrees/backport-2.6
# Create a new branch
git switch --create backport/backport-526-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 066eaeece19d68a9838af933533c4daf38e47fa1
# Push it to GitHub
git push --set-upstream origin backport/backport-526-to-2.6
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.6Then, create a pull request where the |
Member
Author
|
Only Older branches |
lezzago
pushed a commit
that referenced
this pull request
Sep 1, 2023
…526) (#527) * CVE-2023-2976 Fix google-java-format-1.17.0.jar: 1 vulnerabilities Signed-off-by: Sandesh Kumar <kusandes@amazon.com> * fix Signed-off-by: Sandesh Kumar <kusandes@amazon.com> --------- Signed-off-by: Sandesh Kumar <kusandes@amazon.com> Co-authored-by: Sandesh Kumar <kusandes@amazon.com> (cherry picked from commit 066eaee) Co-authored-by: Sandesh Kumar <sandeshkr419@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Fix google-java-format-1.17.0.jar: 1 vulnerabilities
Issues Resolved
Resolves #511
CVE: https://www.mend.io/vulnerability-database/CVE-2023-2976
Check List
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.