Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CVE-2023-2976] Fix google-java-format-1.17.0.jar: 1 vulnerabilities #526

Merged
merged 2 commits into from
Aug 31, 2023

Conversation

sandeshkr419
Copy link
Contributor

@sandeshkr419 sandeshkr419 commented Aug 31, 2023

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

  • 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.

@sandeshkr419 sandeshkr419 changed the title CVE-2023-2976 Fix google-java-format-1.17.0.jar: 1 vulnerabilities [WIP] CVE-2023-2976 Fix google-java-format-1.17.0.jar: 1 vulnerabilities Aug 31, 2023
@sandeshkr419 sandeshkr419 changed the title [WIP] CVE-2023-2976 Fix google-java-format-1.17.0.jar: 1 vulnerabilities [Draft] CVE-2023-2976 Fix google-java-format-1.17.0.jar: 1 vulnerabilities Aug 31, 2023
fix
Signed-off-by: Sandesh Kumar <[email protected]>
@codecov
Copy link

codecov bot commented Aug 31, 2023

Codecov Report

Merging #526 (ef4f31c) into main (8556254) will not change coverage.
The diff coverage is n/a.

@@            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           

@sandeshkr419 sandeshkr419 changed the title [Draft] CVE-2023-2976 Fix google-java-format-1.17.0.jar: 1 vulnerabilities CVE-2023-2976 Fix google-java-format-1.17.0.jar: 1 vulnerabilities Aug 31, 2023
@sandeshkr419 sandeshkr419 changed the title CVE-2023-2976 Fix google-java-format-1.17.0.jar: 1 vulnerabilities [CVE-2023-2976] Fix google-java-format-1.17.0.jar: 1 vulnerabilities Aug 31, 2023
@lezzago lezzago merged commit 066eaee into opensearch-project:main Aug 31, 2023
14 of 16 checks passed
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 <[email protected]>

* fix

Signed-off-by: Sandesh Kumar <[email protected]>

---------

Signed-off-by: Sandesh Kumar <[email protected]>
Co-authored-by: Sandesh Kumar <[email protected]>
(cherry picked from commit 066eaee)
@sandeshkr419 sandeshkr419 deleted the CVE-2023-2976 branch August 31, 2023 19:04
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.8 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.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.8

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.9 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.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.9

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.7 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.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.7

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.4 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.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.4

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.5 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.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.5

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.6 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.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.6

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

@sandeshkr419
Copy link
Contributor Author

Only main (fix merged) and 2.x branch has this vulnerability. Please merge the backport #527

Older branches 2.4-2.9 do not have this vulnerability. We can safely remove those backport tags since they are not required.

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 <[email protected]>

* fix

Signed-off-by: Sandesh Kumar <[email protected]>

---------

Signed-off-by: Sandesh Kumar <[email protected]>
Co-authored-by: Sandesh Kumar <[email protected]>
(cherry picked from commit 066eaee)

Co-authored-by: Sandesh Kumar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

google-java-format-1.17.0.jar: 1 vulnerabilities (highest severity is: 7.1) - autoclosed
3 participants