Closed ddollar closed 5 years ago
Since people are financially incentivized to find and create those vulnerability reports, we'll need to have more information than this. Please also describe:
And any other information that can shed some light on why we should take action.
I don't have much context other than that Github is pinging me about a vulnerability in my app. Tracked it down to nodemon which uses snapdragon which uses braces.
Ok, I believe this is the referenced issue: https://github.com/visionmedia/debug/issues/501.
I am getting alerts from github about mixin-deep vulnerability and it looks like they can be resolved with a snapdragon update in braces.
Any progress on this one? I'm getting the same report now...
└─┬ laravel-mix@3.0.0 └─┬ chokidar@2.0.4 └─┬ braces@2.3.2 └─┬ snapdragon@0.8.1 └─┬ base@0.11.2 └── mixin-deep@1.3.0
this was already requested by #13
I am getting alerts from github about mixin-deep vulnerability and it looks like they can be resolved with a snapdragon update in braces.
This is not a vulnerability, and even if it was it's not possible for it to manifest in braces. Closing in favor of a PR. All unit tests must pass, as well as regression and integration tests in downstream libraries.
The version used (0.8) has a dependency with a vulnerability (debug)
https://nvd.nist.gov/vuln/detail/CVE-2017-16137