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

"High" severity audit alert because of css-what #564

Closed
zackdotcomputer opened this issue Jun 8, 2021 · 8 comments
Closed

"High" severity audit alert because of css-what #564

zackdotcomputer opened this issue Jun 8, 2021 · 8 comments

Comments

@zackdotcomputer
Copy link

Report

Per this security advisory there is a "high risk" DoS risk from the dependency css-what that is fixed by upgrading it to 5.0.1 or higher.

This is appearing if you use svgr because of the dependency chain:

@svgr/webpack > @svgr/plugin-svgo > svgo > css-select > css-what

To Reproduce

Run npm audit on a project that includes @svgr/webpack as a dependency.

Expected behavior

No audit warning should appear

Proposed resolution

I've opened an issue in svgo to resolve the dependency issue there. Once that is closed, the dependency on svgo in @svgr/plugin-svgo should also be updated.

This is likely not that much of a risk since a DoS attack via a dev-dependency used during build is essentially a non-risk, so it's low priority. But, it is causing a scary angry audit risk that might scare off new developers, so I figured it was worth opening this nonetheless.

@open-collective-bot
Copy link

Hey @zackdotcomputer 👋,
Thank you for opening an issue. We'll get back to you as soon as we can.
Please, consider supporting us on Open Collective. We give a special attention to issues opened by backers.
If you use SVGR at work, you can also ask your company to sponsor us ❤️.

@gicontz
Copy link

gicontz commented Jun 8, 2021

Same issue here!

@igloude
Copy link

igloude commented Jun 8, 2021

Thanks for opening this one - we're looking for the same thing here!

@ntucker
Copy link

ntucker commented Jun 9, 2021

Related: #537

@Mister-Hope
Copy link

Any updates?

@stale
Copy link

stale bot commented Aug 29, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Aug 29, 2021
@zackdotcomputer
Copy link
Author

This issue is still active and will be solved by #565

@stale stale bot removed the wontfix label Aug 30, 2021
@gregberge
Copy link
Owner

Fixed in #591

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

6 participants