Nuxt.js: Vulnerability package dependency "defaults-deep"

Created on 7 Feb 2019  路  4Comments  路  Source: nuxt/nuxt.js

Version

v2.4.3

Reproduction link

https://www.npmjs.com/advisories/778

Steps to reproduce

Please fix this vulnerability in your dependency tree:

nuxt > @nuxt/core > @nuxt/server > serve-placeholder > defaults-deep

What is expected ?

0 vulnerabilities found when audit packages.

As no patch is currently available for this vulnerability it is our recommendation to select another module that can provide this functionality.

What is actually happening?

All versions of defaults-deep are vulnerable to prototype pollution. Provided certain input defaults-deep can add or modify properties of the Object prototype. These properties will be present on all objects.

Additional comments?

https://hackerone.com/reports/380878

This bug report is available on Nuxt community (#c8618)
available soon stale

Most helpful comment

For clarification as also described in CVE-2018-16486 the impact is _possibly more depending on the application._ and no nuxt users are affected for sure because options to the middleware are not from user input but only from nuxt.config.

For general:

I submitted the fix to prevent accepting contructor.prototype key on defaults-deep but as it is unlikely to fast merge and publish, I created an alternative package that only does what we want.

All 4 comments

Hi. Thanks for the report. This is being addressed fast.

@pi0 Can you please explain shortly how you fixed that? (I followed the 2 links but ...)

For clarification as also described in CVE-2018-16486 the impact is _possibly more depending on the application._ and no nuxt users are affected for sure because options to the middleware are not from user input but only from nuxt.config.

For general:

I submitted the fix to prevent accepting contructor.prototype key on defaults-deep but as it is unlikely to fast merge and publish, I created an alternative package that only does what we want.

Thanks for your contribution to Nuxt.js!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:

  1. Verify that you can still reproduce the issue in the latest version of nuxt-edge
  2. Comment the steps to reproduce it

Issues that are labeled as 馃晲Pending will not be automatically marked as stale.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mattdharmon picture mattdharmon  路  3Comments

vadimsg picture vadimsg  路  3Comments

surmon-china picture surmon-china  路  3Comments

VincentLoy picture VincentLoy  路  3Comments

shyamchandranmec picture shyamchandranmec  路  3Comments