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

Force version 3.29.0 of org.eclipse.core.runtime to address CVE vulnerabilities #3313

Merged

Conversation

rithin-pullela-aws
Copy link
Contributor

Description

Address CVE vulnerability in plugin/build.gradle: org.eclipse.core.runtime-3.26.100.jar by forcing version 3.29.0

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

  • New functionality includes testing.
  • New functionality has been documented.
  • API changes companion pull request created.
  • Commits are signed per the DCO using --signoff.
  • Public documentation issue/PR created.

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.

@dhrubo-os
Copy link
Collaborator

Cool, looks like Mend Security Check is Successful. While you are working on CVE, let's look into this too: #1865

@rithin-pullela-aws rithin-pullela-aws temporarily deployed to ml-commons-cicd-env-require-approval December 31, 2024 19:45 — with GitHub Actions Inactive
@opensearch-trigger-bot
Copy link
Contributor

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-3313-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7af78b059666a198711a84f083dc48c1745fcc8d
# Push it to GitHub
git push --set-upstream origin backport/backport-3313-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-3313-to-2.x.

@dhrubo-os
Copy link
Collaborator

backport is failing. @rithin-pullela-aws can you check?

rithin-pullela-aws added a commit to rithin-pullela-aws/ml-commons that referenced this pull request Jan 14, 2025
…erabilities (opensearch-project#3313)

Signed-off-by: rithin-pullela-aws <[email protected]>
(cherry picked from commit 7af78b0)
rithin-pullela-aws added a commit to rithin-pullela-aws/ml-commons that referenced this pull request Jan 16, 2025
…erabilities (opensearch-project#3313)

Signed-off-by: rithin-pullela-aws <[email protected]>
(cherry picked from commit 7af78b0)
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.

3 participants