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

npm audit security issue with handlebars 4.0.x #176

Closed
cholz opened this issue Sep 25, 2019 · 8 comments
Closed

npm audit security issue with handlebars 4.0.x #176

cholz opened this issue Sep 25, 2019 · 8 comments
Assignees
Labels

Comments

@cholz
Copy link

cholz commented Sep 25, 2019

NPM Packages built with "audit" will fail, due a handlebars security issue.
Updating the handlebars dependency to 4.3.1 should solve the issue.

                       === npm audit security report ===


                                 Manual Review
             Some vulnerabilities require your attention to resolve

          Visit https://go.npm.me/audit-guide for additional guidance


  High            Prototype Pollution

  Package         handlebars

  Patched in      >=4.3.0

  Dependency of   hbs

  Path            hbs > handlebars

  More info       https://nodesecurity.io/advisories/1164

found 1 high severity vulnerability in 1765970 scanned packages
  1 vulnerability requires manual review. See the full report for details.
@dougwilson
Copy link
Contributor

dougwilson commented Sep 25, 2019

Thank you for the report. Looks like it was just published yesterday. I will look at what changes need to be done to upgrade; I seem to recall there was an incompatibility moving to the 4.1.x series I had on my backlog to resolve, but I guess I need to do that today 👍

@Naktibalda
Copy link

I hope that this issue can be fixed in a minor or patch release, bumping version number to 5.0.0 would require other libraries to update their hbs version constraint.

@dougwilson
Copy link
Contributor

Yes, I agree. I would like to figure out one of three paths is all (maybe there are more)

  1. What can we do to upgrade to latest handlebars but keep this a 4.x release so folks get it automatically with semver ranges.
  2. Maybe even if we can backport the fix to the 4.0.x branch of handlebars (this was done with previous patches) thus we can bump the patch version.
  3. Last case, document the breaking changes and migration guide and release as 5.0 and people will need to migrate to address the issue.

Those are my thoughts, at least, in order of own own preferences.

@dougwilson
Copy link
Contributor

I have traced through the one test failure and created a bug in the handlebars project for it: handlebars-lang/handlebars.js#1562

Our test suite is not really great at coverage, so I am just going through all the changes between the 4.0.14 handlebars and 4.3.1 currently. Even though I filed the bug above, I believe I found a work-around, so it won't end up as a blocker thankfully.

@dougwilson
Copy link
Contributor

Just a heads-up for those looking here, there is yet another security issue handlebars is working to fix: handlebars-lang/handlebars.js#1563 . I continue to work towards the upgrade here, which will make us ready for when that new handlebars version will drop.

@dougwilson
Copy link
Contributor

dougwilson commented Sep 27, 2019

A new version of this module, hbs, will be published with the updated handlebars dependency within the next 10 hours.

@dougwilson
Copy link
Contributor

Ok, handlebars 4.3.3 is published now, so that will be the upgrade target. Also, AFAICT there isn't anything breaking when used through this module, so this will be a patch release for hbs.

@dougwilson
Copy link
Contributor

Published as 4.0.5 with handlebars 4.3.3

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.

3 participants