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

fix: update update-notifier to resolve dot-prop vulnerability #1585

Closed
wants to merge 0 commits into from
Closed

fix: update update-notifier to resolve dot-prop vulnerability #1585

wants to merge 0 commits into from

Conversation

cmdcarini
Copy link

This updates the version of update-notifier to resolve the vulnerability present in the existing version's dot-prop dependency. This resolves #1584 .

References

Closes #1584
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116

@cmdcarini cmdcarini requested a review from a team as a code owner July 30, 2020 18:29
@ljharb
Copy link
Contributor

ljharb commented Jul 30, 2020

It's tough to tell in the diff; do any of these bump major versions such that engines support would change?

@cmdcarini
Copy link
Author

Indeed it would appear it would, per the release notes, v3 of update-notifier removes support for Node v6

@cmdcarini
Copy link
Author

@moustafab
Copy link

@cmdcarini I was working on sorting this issue out this morning, and saw this issue/PR pop up. One issue you might have is the dependent package is also there in libnpx.

@cmdcarini
Copy link
Author

@cmdcarini I was working on sorting this issue out this morning, and saw this issue/PR pop up. One issue you might have is the dependent package is also there in libnpx.

I noticed this too, figured there's room for another PR, after they patch

@cmdcarini
Copy link
Author

@ruyadorno | @isaacs | ${someOtherNPMOfficial} are there any updates on triaging this to be reviewed/merged?

@ruyadorno
Copy link
Contributor

@cmdcarini thank you for taking the time to put this together 😊

We are aware of the issue and planning to have a patch release of v6 that solves the problem sometime soon 👍

@ruyadorno
Copy link
Contributor

ruyadorno commented Aug 3, 2020

Note: We can't land this PR in its current state since we can't drop support to node6 in npm6.

That said, I'm not sure yet what the answer will be 🤔 Sorry I can't be more helpful at the moment, we def appreciate the contribution so I just wanted to leave you the quick reply 😊

@cmdcarini
Copy link
Author

Note: We can't land this PR in its current state since we can't drop support to node6 in npm6.

That said, I'm not sure yet what the answer will be 🤔 Sorry I can't be more helpful at the moment, we def appreciate the contribution so I just wanted to leave you the quick reply 😊

Awesome! Thanks much for your reply

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Vulnerability present in version of dot-prop used by npm
4 participants