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

Security Vulnerabilities with globby, pacote and conventional-changelog-core versions #2579

Closed
vic-nik opened this issue May 11, 2020 · 4 comments
Labels

Comments

@vic-nik
Copy link

vic-nik commented May 11, 2020

The current versions of the following npm packages have security vulnerabilities. Can you please upgrade them to the latest version?

  • globby (used by @lerna/create@3.18.5)
  • pacote (used @lerna/add@3.20.0)
  • conventional-changelog-core (used @lerna/conventional-commits@3.18.5)

The vulnerable packages in dependecy tree are:
kind-of v. < 6.0.3
minimist v. < 0.2.1

Below are related dependency trees:

-- lerna@3.20.2 +-- @lerna/add@3.20.0 | -- @lerna/command@3.18.5
| -- clone-deep@4.0.1 | +-- kind-of@6.0.3 | -- shallow-clone@3.0.1
| -- kind-of@6.0.3 deduped -- @lerna/create@3.18.5
-- globby@9.2.0 -- fast-glob@2.2.7
-- micromatch@3.1.10 +-- braces@2.3.2 | +-- fill-range@4.0.0 | | -- is-number@3.0.0
| | -- kind-of@3.2.2 | -- snapdragon-node@2.1.1
| +-- define-property@1.0.0
| | -- is-descriptor@1.0.2 | | +-- is-accessor-descriptor@1.0.0 | | | -- kind-of@6.0.3 deduped
| | +-- is-data-descriptor@1.0.0
| | | -- kind-of@6.0.3 deduped | | -- kind-of@6.0.3 deduped
| -- snapdragon-util@3.0.1 | -- kind-of@3.2.2
+-- define-property@2.0.2
| -- is-descriptor@1.0.2 | +-- is-accessor-descriptor@1.0.0 | | -- kind-of@6.0.3 deduped
| +-- is-data-descriptor@1.0.0
| | -- kind-of@6.0.3 deduped | -- kind-of@6.0.3 deduped
+-- extglob@2.0.4
| -- define-property@1.0.0 | -- is-descriptor@1.0.2
| +-- is-accessor-descriptor@1.0.0
| | -- kind-of@6.0.3 deduped | +-- is-data-descriptor@1.0.0 | | -- kind-of@6.0.3 deduped
| -- kind-of@6.0.3 deduped +-- kind-of@6.0.3 deduped +-- nanomatch@1.2.13 | -- kind-of@6.0.3 deduped
-- snapdragon@0.8.2 +-- base@0.11.2 | +-- cache-base@1.0.1 | | +-- has-value@1.0.0 | | | -- has-values@1.0.0
| | | -- kind-of@4.0.0 | | -- to-object-path@0.3.0
| | -- kind-of@3.2.2 | +-- class-utils@0.3.6 | | -- static-extend@0.1.2
| | -- object-copy@0.1.0 | | -- kind-of@3.2.2
| -- define-property@1.0.0 | -- is-descriptor@1.0.2
| +-- is-accessor-descriptor@1.0.0
| | -- kind-of@6.0.3 deduped | +-- is-data-descriptor@1.0.0 | | -- kind-of@6.0.3 deduped
| -- kind-of@6.0.3 deduped -- define-property@0.2.5
-- is-descriptor@0.1.6 +-- is-accessor-descriptor@0.1.6 | -- kind-of@3.2.2
+-- is-data-descriptor@0.1.4
| -- kind-of@3.2.2 -- kind-of@5.1.0

-- lerna@3.20.2 +-- @lerna/add@3.20.0 | -- @evocateur/pacote@9.6.5
| -- mkdirp@0.5.1 | -- minimist@0.0.8
+-- @lerna/create@3.18.5
| -- @lerna/child-process@3.16.5 | -- strong-log-transformer@2.1.0
| -- minimist@1.2.0 -- @lerna/version@3.20.2
-- @lerna/conventional-commits@3.18.5 +-- conventional-changelog-core@3.2.3 | +-- conventional-changelog-writer@4.0.11 | | -- handlebars@4.7.2
| | -- optimist@0.6.1 | | -- minimist@0.0.8 deduped
| +-- get-pkg-repo@1.4.0
| | -- meow@3.7.0 | | -- minimist@1.2.0
| +-- git-raw-commits@2.0.0
| | -- meow@4.0.1 | | -- minimist@1.2.0
| -- git-semver-tags@2.0.3 | -- meow@4.0.1
| -- minimist@1.2.0 -- conventional-recommended-bump@5.0.1
-- meow@4.0.1 -- minimist@1.2.0

Executable Version
lerna --version 3.20.2
npm --version 6.10.1
node --version 10.16.0
OS Version
Windows 10 1607
@kibertoad
Copy link

Most likely the problem with updating conventional-changelog-core is that latest major version is Node 10+, while Lerna is Node 8+. So this would require a major version bump from Lerna side, although since Node 8 is deprecated already, that doesn't sound like a big deal.

@musbaig
Copy link

musbaig commented Jul 2, 2020

Any updates on when this issue might get resolved? We'd like to use lerna for our current project, but, Nexus is flagging and quarantining lerna. We tried going a few minor and at least one major version back, but, to no avail. Note, the latest version, v3.22.1, has the same issue.

@github-actions
Copy link

github-actions bot commented Jun 3, 2022

Hi Folks 👋

You may or may not know that lerna is now under the stewardship of Nrwl (announcement here #3121), a company with a long history of not just producing valuable open-source software (OSS), but also backing others (at the time of writing, Nrwl has donated over $50,000 to OSS it hasn't created, see https://opencollective.com/nx for full details).

Quite simply, Nrwl ❤️ OSS, and is committed to making lerna the best it can be. We use it ourselves.

In order to take this awesome project forward from its current state, it is important that we focus our finite resources on what is most important to lerna users in 2022.

With that in mind, we have identified this issue as being potentially stale due to its age and/or lack of recent activity.


Next steps:

We want to give you some time to read through this comment and take action per one of the steps outlined below, so for the next 14 days we will not make any further updates to this issue.

@vic-nik as the original author of this issue, we are looking to you to update us on the latest state of this as it relates to the latest version of lerna.

Please choose one of the steps below, depending on what type of issue this is:

  • A) If this issue relates to a potential BUG in the latest version of lerna:

  • B) If this issue is a FEATURE request to be added to the latest version of lerna:

    • Simply comment back on this thread so that we know you still want us to consider the request for the latest version of lerna.
  • C) If this issue is a QUESTION which is applicable to latest version of lerna:

  • D) If this issue is no longer applicable to the latest version of lerna:

    • Please close the issue.

If we do not hear from @vic-nik on this thread within the next 14 days, we will automatically close this issue.

If you are another user impacted by this issue but it ends up being closed as part of this process, we still want to hear from you! Please simply head over to our new issue templates and fill out all the requested details on the template which applies to your situation:

https://github.com/lerna/lerna/issues/new/choose

Thank you all for being a part of this awesome community, we could not be more excited to help move things forward from here 🙏 🚀

@JamesHenry
Copy link
Member

Hi Folks, following on from the note above, looking at this issue specifically the relevant packages have all since been patched and there are no such audit warnings when using our latest v5 packages we released since we took over.

Many thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants