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 Vulnerabilities in package-lock.json #116

Closed
benabus opened this issue Mar 16, 2021 · 2 comments
Closed

Security Vulnerabilities in package-lock.json #116

benabus opened this issue Mar 16, 2021 · 2 comments
Assignees

Comments

@benabus
Copy link

benabus commented Mar 16, 2021

We've been notified by our enterprise github that there are numerous security vulnerabilities in package-lock.json:

ini Known security vulnerability in 1.3.5
kind-of Known security vulnerability in 6.0.2
node-uuid Known security vulnerability in 1.4.0
serialize-javascript Known security vulnerability in 1.9.1
yargs-parser Known security vulnerability in 5.0.0 
@w00fz
Copy link
Member

w00fz commented Mar 18, 2021

Usually these are on 3rd party nested dependencies.
I’ll give flex objects an update to use latest or everything.

@w00fz
Copy link
Member

w00fz commented Mar 18, 2021

This is sorted now @benabus but the truth is, none of those reported vulnerabilities have any affect on the distributed JS from flex-objects. The bot is purely complaining about the package-lock.json and yarn.lock, which i have now updated accordingly.

As a precaution I have recompiled the JS but as expected, the source code has not changed at all.

Thanks for the heads-up and I'm glad to be on the safe side here, but I wouldn't worry about it having any security effect on your end.

Cheers,

@w00fz w00fz closed this as completed Mar 18, 2021
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