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

Please update acorn to 6.4.1, or 7.1.1 to resolve vulnerability in acorn #375

Open
IdanAdar opened this issue Mar 8, 2020 · 15 comments
Open

Comments

@IdanAdar
Copy link

IdanAdar commented Mar 8, 2020

See advisory from npm: https://www.npmjs.com/advisories/1488

@nmccready

@Rafalsky
Copy link

Rafalsky commented Mar 9, 2020

This is fixed on master branch.

Commit: 8a22ecc

Just need to be tagged.

@Ionaru
Copy link

Ionaru commented Mar 9, 2020

That commit was over a year ago, what's the reason no new version has been tagged since then?

@nmccready
Copy link
Collaborator

That commit was over a year ago, what the reason no new version has been tagged since then?

Looks like there was no release as this was primarily linting changes.

Also this is neither mine or @phated 's full time job. If you guys see issues please make PR's.

Even with @phated 's changes it appears acorn is still under 7.1.1 and needs to be fixed in @gulp-sourcemaps/identity

❯ yarn why acorn
yarn why v1.21.1
[1/4] 🤔  Why do we have the module "acorn"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "acorn@5.7.3"
info Has been hoisted to "acorn"
info Reasons this module exists
   - Specified in "dependencies"
   - Hoisted from "@gulp-sourcemaps#identity-map#acorn"
   - Hoisted from "eslint#espree#acorn"
info Disk size without dependencies: "588KB"
info Disk size with unique dependencies: "588KB"
info Disk size with transitive dependencies: "588KB"
info Number of shared dependencies: 0
=> Found "acorn-jsx#acorn@3.3.0"
info This module exists because "eslint#espree#acorn-jsx" depends on it.
info Disk size without dependencies: "676KB"
info Disk size with unique dependencies: "676KB"
info Disk size with transitive dependencies: "676KB"
info Number of shared dependencies: 0
✨  Done in 0.38s.

~/code/thirdparties/gulp-sourcemaps master
❯ yarn info acorn version
yarn info v1.21.1
6.4.1

@Ionaru
Copy link

Ionaru commented Mar 9, 2020

@Ionaru
Copy link

Ionaru commented Mar 9, 2020

This module has acorn in its dependencies as well: https://github.com/gulp-sourcemaps/gulp-sourcemaps/blob/master/package.json#L26

@nmccready
Copy link
Collaborator

As you can see this is going to be more difficult than just bumping.

https://travis-ci.org/gulp-sourcemaps/identity-map/jobs/660134323?utm_medium=notification&utm_source=github_status

6.X branch of acorn still has not resolved the issues. gulp-sourcemaps is trying to support node 6.X - 10.X.

To get things working correctly acorn is going to need to patch 6.X .

@phated , should we drop acorn or drop 6.X support for node ?

@nmccready nmccready changed the title Please update acorn to 7.1.1 to resolve vulnerability in acorn Please update acorn to 6.4.1, or 7.1.1 to resolve vulnerability in acorn Mar 9, 2020
@nmccready
Copy link
Collaborator

We'll be targeting 6.4.1 as it should work with Node 6.

@hansnull

This comment has been minimized.

@nmccready
Copy link
Collaborator

NodeJS 6 is not maintained anymore, or am I wrong?

That's not my battle but gulp-sourcemaps has always supported many older versions of node. It is only within the year where we cut out 4, 0.12, and 0.10 .

ask @phated

@nmccready
Copy link
Collaborator

#376

@phated
Copy link
Contributor

phated commented Mar 9, 2020

ask @phated

If you leave users stranded on old versions of your software because you can't be bothered to support a few older versions of the runtime, then you are a bad maintainer.

@IdanAdar
Copy link
Author

@nmccready Please let us know once the new build reaches npm so we can pull it proper.

@gian1200
Copy link

It seems to be "fixable" now buy running npm audit fix 🤷‍♂

@limitedmage
Copy link

The PR was merged but no release has been published to NPM yet?

@valadas
Copy link

valadas commented Jun 24, 2020

I am in the same situation but npm audit fix did not resolve it.

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

No branches or pull requests

9 participants