-
Notifications
You must be signed in to change notification settings - Fork 229
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
Medium severity vulnerability in chownr
dependency
#1127
Comments
I have reported to snyk re isaacs/chownr#14 and they are going to look into it. It appears like this will either be removes as a vulnerability in snyk for 1.1.0 OR it will always be a vulnerability that fundamentally cant be fixed I got this reply from Synk yesterday
|
Blocked pending outcome of Snyk discussion. |
I've emailed Snyk for an update. |
Response from Snyk: "Thank you for your report! We've looked into the issue and decided to split it into two vulnerabilities, one medium severity that is fixed in 1.1.0, and another one with a low severity, unfixed as serves as an informational vulnerability." Confirmed: We should be able to resolve the Medium severity vulnerability by locking into 1.1.0 of chownr, and we should be able to mark the low severity vulnerability as 'safe' in the Snyk admin UI. |
As discussed in person, this doesn't seem to be available to us unless using Yarn. |
Thanks @ChrisBAshton and @dr3 for your report on this. Snyk addressed the vulnerability report and maintainer's comments on the issue. |
Thanks very much for the update @lirantal -- I think we have a bit of a dependency chain, so we'll keep an eye on it & open issues in other repos as necessary. |
Describe the bug
From Snyk:
The vulnerability is introduced via several dependencies - not just Razzle - so may be difficult to sort out through dependency replacement/upgrades (though we should try that first).
If all else fails, we can try locking to a fixed version as we did in event-stream.
To Reproduce
Steps to reproduce the behavior:
npm install snyk
snyk auth
(can't use Snyk otherwise)snyk test
Expected behavior
There should be no vulnerabilities.
The text was updated successfully, but these errors were encountered: