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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vulnerability in y18n (prototype pollution) #99

Closed
xiniria opened this issue Nov 19, 2020 · 5 comments
Closed

Vulnerability in y18n (prototype pollution) #99

xiniria opened this issue Nov 19, 2020 · 5 comments
Assignees

Comments

@xiniria
Copy link
Contributor

xiniria commented Nov 19, 2020

Expected Behavior

When using npq (your own tool! 馃構) to install lockfile-lint, it pointed out that it has 1 vulnerability, according to Snyk's Vuln DB. Actually this vulnerability is a prototype pollution in y18n@4.0.0, which is a dependency of yargs@15.4.1. It is a known vulnerability and it has been fixed a few weeks ago. Updating yargs to the latest version (16.1.1) updates y18n to version 5.0.5 and fixes the issue.

Current Behavior

Vulnerability in dependency.

Possible Solution

Update yargs to version 16.1.1.

Your Environment

  • Library Version used: 4.3.7
  • Node.js version (e.g. Node.js 5.4): 15.2.0
  • Operating System and version (desktop or mobile): macOS Catalina 10.15.7
@xiniria xiniria changed the title Vulnerability in y18n (prototype pollution) Vulnerability in y18n (prototype pollution) Nov 19, 2020
@xiniria
Copy link
Contributor Author

xiniria commented Nov 19, 2020

I just realized that the Snyk bot already created a PR for that: #98

@lirantal lirantal self-assigned this Nov 19, 2020
@lirantal
Copy link
Owner

Indeed it created, but thank you so much for calling this out and making sure I track it!
You're a security hero, sir! 馃 馃挏

@xiniria
Copy link
Contributor Author

xiniria commented Nov 20, 2020

@lirantal The publish job failed on the CI so there is no new version after this PR, could you check what happened?

@lirantal
Copy link
Owner

Yep, I know. It's because the lockfile didn't get properly updated. I am on a temporary macbook right now so I don't have a clone of the project and the environment to fix it. If you wanted to submit a PR that updates the lockfile I'll gladly merge it, as I'll only get to this later next week.

@xiniria
Copy link
Contributor Author

xiniria commented Nov 21, 2020

Done in #100.

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

No branches or pull requests

2 participants