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

Medium severity vulnerability in chownr dependency #1127

Closed
1 task done
ChrisBAshton opened this issue Jan 5, 2019 · 7 comments
Closed
1 task done

Medium severity vulnerability in chownr dependency #1127

ChrisBAshton opened this issue Jan 5, 2019 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@ChrisBAshton
Copy link
Contributor

Describe the bug
From Snyk:

✗ Medium severity vulnerability found in chownr
  Description: Time of Check Time of Use (TOCTOU)
  Info: https://snyk.io/vuln/npm:chownr:20180731
  Introduced through: speculate@1.7.4, compression-webpack-plugin@2.0.0, razzle@2.4.0, brotli-webpack-plugin@1.0.0
  From: speculate@1.7.4 > tar-fs@1.16.3 > chownr@1.1.1
  From: compression-webpack-plugin@2.0.0 > cacache@11.3.1 > chownr@1.1.1
  From: razzle@2.4.0 > uglifyjs-webpack-plugin@1.2.4 > cacache@10.0.4 > chownr@1.1.1
  and 8 more...

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:

  1. npm install snyk
  2. snyk auth (can't use Snyk otherwise)
  3. snyk test
  4. See output

Expected behavior
There should be no vulnerabilities.

  • Initially labelled with "bug"
@ChrisBAshton ChrisBAshton added bug Something isn't working Dependency issue Refinement Needed This is ready for refinement. It shouldn't be worked on until it has been refined by Dev & Test. labels Jan 5, 2019
@dr3
Copy link
Contributor

dr3 commented Jan 5, 2019

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

Hi Drew
Thank you for reaching out to report the issue. 
We will look into it, and update the DB accordingly. CCing Benji to follow up on the findings.

Thanks again!
Danny

@ChrisBAshton ChrisBAshton added the external blocked Blocked by an external dependency label Jan 7, 2019
@ChrisBAshton
Copy link
Contributor Author

Blocked pending outcome of Snyk discussion.

@ChrisBAshton ChrisBAshton self-assigned this Jan 11, 2019
@ChrisBAshton
Copy link
Contributor Author

I've emailed Snyk for an update.

@ChrisBAshton
Copy link
Contributor Author

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:

screen shot 2019-01-11 at 17 13 41

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.

@ChrisBAshton ChrisBAshton removed their assignment Jan 11, 2019
@ChrisBAshton ChrisBAshton removed Refinement Needed This is ready for refinement. It shouldn't be worked on until it has been refined by Dev & Test. external blocked Blocked by an external dependency labels Jan 11, 2019
@bcmn bcmn self-assigned this Jan 11, 2019
@bcmn
Copy link
Contributor

bcmn commented Jan 11, 2019

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.

@lirantal
Copy link

Thanks @ChrisBAshton and @dr3 for your report on this.

Snyk addressed the vulnerability report and maintainer's comments on the issue.
Upgrading to chownr version >= 1.1.1 should not report any vulnerabilities with chownr.

@bcmn bcmn closed this as completed Jan 16, 2019
@bcmn
Copy link
Contributor

bcmn commented Jan 16, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants