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 2022-3517] Bump minimatch to 3.0.5 and [IBM X-Force ID: 220063] unset-value to 2.0.1 #2640

Merged
merged 5 commits into from
Oct 22, 2022

Conversation

himsgupta1122
Copy link
Contributor

@himsgupta1122 himsgupta1122 commented Oct 21, 2022

Signed-off-by: himsgupta1122 [email protected]

Description

IBM X-Force ID: 220063

  • Unset Value: Image contains unset value package version 1.0.1 and this has been resolved with version 2.0.1

CVE 2022-3517

  • Minimatch Package : Image contains 3.0.4 which has an issue and has been fixed with version 3.0.5

Issues Resolved

[List any issues this PR will resolve]

Check List

  • All tests pass
    • yarn test:jest
    • yarn test:jest_integration
    • yarn test:ftr
  • New functionality includes testing.
  • New functionality has been documented.
  • Update CHANGELOG.md
  • Commits are signed per the DCO using --signoff

@himsgupta1122 himsgupta1122 requested a review from a team as a code owner October 21, 2022 00:54
@himsgupta1122 himsgupta1122 force-pushed the 2.3.1 branch 2 times, most recently from 8b29d41 to 841b00e Compare October 21, 2022 00:56
@himsgupta1122 himsgupta1122 changed the title [CVE 2022-3517] Update minimatch to 3.0.5 [CVE 2022-3517] Update minimatch to 3.0.5 and unset-value to 2.0.1 Oct 21, 2022
@himsgupta1122 himsgupta1122 changed the title [CVE 2022-3517] Update minimatch to 3.0.5 and unset-value to 2.0.1 [CVE 2022-3517] Bump minimatch to 3.0.5 and unset-value to 2.0.1 Oct 21, 2022
@codecov-commenter
Copy link

codecov-commenter commented Oct 21, 2022

Codecov Report

❗ No coverage uploaded for pull request base (main@8d5e504). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2640   +/-   ##
=======================================
  Coverage        ?   66.81%           
=======================================
  Files           ?     3207           
  Lines           ?    61148           
  Branches        ?     9315           
=======================================
  Hits            ?    40856           
  Misses          ?    18060           
  Partials        ?     2232           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@himsgupta1122 himsgupta1122 changed the title [CVE 2022-3517] Bump minimatch to 3.0.5 and unset-value to 2.0.1 [CVE 2022-3517] Bump minimatch to 3.0.5 and [IBM X-Force ID: 220063] unset-value to 2.0.1 Oct 21, 2022
@seraphjiang seraphjiang added the Mend: dependency security vulnerability Security vulnerability detected by Mend label Oct 21, 2022
package.json Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
ZilongX
ZilongX previously approved these changes Oct 21, 2022
@himsgupta1122 himsgupta1122 requested review from ZilongX and ananzh and removed request for zhongnansu, kristenTian and ZilongX October 21, 2022 17:26
ananzh
ananzh previously approved these changes Oct 21, 2022
Copy link
Member

@ananzh ananzh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for fixing CVEs for customer!

@ananzh
Copy link
Member

ananzh commented Oct 21, 2022

I think you might need to add tags for backport. Does these CVEs affect 1.x? Do we need to backport to 1.x? Do we have any conflicts there?

@himsgupta1122 himsgupta1122 dismissed stale reviews from ananzh and ZilongX via 371828f October 21, 2022 17:56
@himsgupta1122 himsgupta1122 requested review from ananzh and removed request for ananzh October 21, 2022 18:00
@himsgupta1122
Copy link
Contributor Author

PR looks good. Thanks for the fix. @himsgupta1122 Does it need to be backport to 2.x? If so, please add a label backport 2.x so it will trigger the auto backport PR

yes, but I dont see the option. Please add the label. Thanks

@ananzh ananzh added the cve Security vulnerabilities detected by Dependabot or Mend label Oct 22, 2022
@zhongnansu zhongnansu merged commit 68baac1 into opensearch-project:main Oct 22, 2022
opensearch-trigger-bot bot pushed a commit that referenced this pull request Oct 22, 2022
…unset-value to 2.0.1 (#2640)

* Update CVE 2022-3517 minimatch to 3.0.5
* enforce unset-value to 2.0.1
* version semver update and combining changelogs
* adding minimatch sub-dep resolution
Signed-off-by: himsgupta1122 <[email protected]>

(cherry picked from commit 68baac1)
@ananzh ananzh added the v2.4.0 'Issues and PRs related to version v2.4.0' label Oct 23, 2022
@kavilla kavilla linked an issue Oct 24, 2022 that may be closed by this pull request
1 task
joshuarrrr pushed a commit that referenced this pull request Oct 27, 2022
…unset-value to 2.0.1 (#2640) (#2654)

* Update CVE 2022-3517 minimatch to 3.0.5
* enforce unset-value to 2.0.1
* version semver update and combining changelogs
* adding minimatch sub-dep resolution
Signed-off-by: himsgupta1122 <[email protected]>

(cherry picked from commit 68baac1)

Co-authored-by: himsgupta1122 <[email protected]>
Co-authored-by: Zhongnan Su <[email protected]>
@opensearch-trigger-bot
Copy link
Contributor

The backport to 1.x failed:

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

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
pushd ../.worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-2640-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 68baac19664decd8b1cb0a35fa82ba0e9af4f658
# Push it to GitHub
git push --set-upstream origin backport/backport-2640-to-1.x
# Go back to the original working tree
popd
# 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-2640-to-1.x.

joshuarrrr pushed a commit to joshuarrrr/OpenSearch-Dashboards that referenced this pull request Nov 29, 2022
…unset-value to 2.0.1 (opensearch-project#2640)

* Update CVE 2022-3517 minimatch to 3.0.5
* enforce unset-value to 2.0.1
* version semver update and combining changelogs
* adding minimatch sub-dep resolution
Signed-off-by: himsgupta1122 <[email protected]>

(cherry picked from commit 68baac1)
joshuarrrr pushed a commit to joshuarrrr/OpenSearch-Dashboards that referenced this pull request Nov 29, 2022
…unset-value to 2.0.1 (opensearch-project#2640)

* Update CVE 2022-3517 minimatch to 3.0.5
* enforce unset-value to 2.0.1
* version semver update and combining changelogs
* adding minimatch sub-dep resolution
Signed-off-by: himsgupta1122 <[email protected]>

(cherry picked from commit 68baac1)
joshuarrrr added a commit that referenced this pull request Nov 30, 2022
…unset-value to 2.0.1 (#2640) (#2946)

* Update CVE 2022-3517 minimatch to 3.0.5
* enforce unset-value to 2.0.1
* version semver update and combining changelogs
* adding minimatch sub-dep resolution
Signed-off-by: himsgupta1122 <[email protected]>

(cherry picked from commit 68baac1)

Co-authored-by: himsgupta1122 <[email protected]>
joshuarrrr added a commit to joshuarrrr/OpenSearch-Dashboards that referenced this pull request Nov 30, 2022
…unset-value to 2.0.1 (opensearch-project#2640) (opensearch-project#2946)

* Update CVE 2022-3517 minimatch to 3.0.5
* enforce unset-value to 2.0.1
* version semver update and combining changelogs
* adding minimatch sub-dep resolution
Signed-off-by: himsgupta1122 <[email protected]>

(cherry picked from commit 68baac1)

Co-authored-by: himsgupta1122 <[email protected]>
(cherry picked from commit 21a9e7f)
ananzh pushed a commit that referenced this pull request Dec 1, 2022
…unset-value to 2.0.1 (#2640) (#2946) (#2972)

* Update CVE 2022-3517 minimatch to 3.0.5
* enforce unset-value to 2.0.1
* version semver update and combining changelogs
* adding minimatch sub-dep resolution
Signed-off-by: himsgupta1122 <[email protected]>

(cherry picked from commit 68baac1)

Co-authored-by: himsgupta1122 <[email protected]>
(cherry picked from commit 21a9e7f)
sipopo pushed a commit to sipopo/OpenSearch-Dashboards that referenced this pull request Dec 16, 2022
…unset-value to 2.0.1 (opensearch-project#2640)

* Update CVE 2022-3517 minimatch to 3.0.5
* enforce unset-value to 2.0.1
* version semver update and combining changelogs
* adding minimatch sub-dep resolution
Signed-off-by: himsgupta1122 <[email protected]>

Signed-off-by: Sergey V. Osipov <[email protected]>
Arpit-Bandejiya pushed a commit to Arpit-Bandejiya/OpenSearch-Dashboards that referenced this pull request Jan 13, 2023
…unset-value to 2.0.1 (opensearch-project#2640)

* Update CVE 2022-3517 minimatch to 3.0.5
* enforce unset-value to 2.0.1
* version semver update and combining changelogs
* adding minimatch sub-dep resolution
Signed-off-by: himsgupta1122 <[email protected]>

Signed-off-by: Arpit Bandejiya <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x cve Security vulnerabilities detected by Dependabot or Mend Mend: dependency security vulnerability Security vulnerability detected by Mend v1.3.7 v2.4.0 'Issues and PRs related to version v2.4.0'
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IBM X-Force ID: 220063 Unset-value HIGH Severity Vulnerability