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

Some medium+ vulnerable packages #10

Open
trycontrolmymind opened this issue Nov 27, 2018 · 1 comment
Open

Some medium+ vulnerable packages #10

trycontrolmymind opened this issue Nov 27, 2018 · 1 comment

Comments

@trycontrolmymind
Copy link

I've tried snyk to test my repo's and fond some
What you think about them?

Tested 110 dependencies for known vulnerabilities, found 6 vulnerabilities, 23 vulnerable paths.
? ✗ 14 Low vulnerabilities introduced in hoek
    Info: https://snyk.io/package/npm/hoek/2.16.3

? ✗ Medium severity vuln found in [email protected], introduced via [email protected]
    Description: Uninitialized Memory Exposure
    Info: https://snyk.io/vuln/npm:stringstream:20180511
    From: [email protected] > [email protected] > [email protected]

? ✗ Medium severity vuln found in [email protected], introduced via [email protected]
    Description: Insecure Randomness
    Info: https://snyk.io/vuln/npm:cryptiles:20180710

? ✗ Medium severity vuln found in [email protected], introduced via [email protected]
    Description: Insecure Randomness
    Info: https://snyk.io/vuln/npm:cryptiles:20180710
    From: [email protected] > [email protected]

? ✗ Medium severity vuln found in [email protected], introduced via [email protected]
    Description: Insecure Randomness
    Info: https://snyk.io/vuln/npm:cryptiles:20180710
    From: [email protected] > [email protected] > [email protected]

? ✗ Medium severity vuln found in [email protected], introduced via [email protected]
    Description: Insecure Randomness
    Info: https://snyk.io/vuln/npm:cryptiles:20180710
    From: [email protected] > [email protected] > [email protected] > [email protected]

Seem's that we can try to fix with upgrading?

@xogeny
Copy link
Collaborator

xogeny commented Nov 27, 2018

This repository doesn't directly depend on any of these. It seems to me these upgrades are the responsibility of upstream packages.

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