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

Security Vulnerability Issue #324

Open
iadibar opened this issue Dec 16, 2020 · 4 comments
Open

Security Vulnerability Issue #324

iadibar opened this issue Dec 16, 2020 · 4 comments

Comments

@iadibar
Copy link

iadibar commented Dec 16, 2020

Im using webfont package that dependent on meow. meow dependent on yargs-parser.
when I scan my app (with Veracode sca) I getting Command Injection Vulnerability from yargs-parser version 10.1.0,
They suggest updating yargs-parser to [email protected], so that it is not vulnerable version, but I can not do it in my code because the dependencies are inside your code so I'll be happy if you can update your meow to latest version(inside webfont package.json
dependency).

screen shot from veracode SCA
error : Prototype Pollution yargs-parser is vulnerable to prototype pollution. The attack exists as it does not properly sanitize the key value provided by users, allowing the malicious properties of Object.prototype to be parsed or modified using a proto payload.
Image 16-12-2020 at 11 18

@ghost
Copy link

ghost commented Jan 5, 2021

This is a dupe of #302 - it's fixed in the master branch, just waiting for a release.

@jimmyandrade
Copy link
Collaborator

@iadibar thanks for reporting. Webfont 10 was released, and I think that this issue was resolved. Could you please check it out? Thanks!

@jimmyandrade
Copy link
Collaborator

jimmyandrade commented Apr 9, 2021

This is a dupe of #302 - it's fixed in the master branch, just waiting for a release.

@iainbethune Thanks for helping us with issues maintenance! :)

@wkeese
Copy link

wkeese commented Feb 2, 2022

Looks like this is fixed in 11.2.26 (or earlier), I think you can close this ticket.

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

3 participants