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

Reported vulnerability in dependency randomatic (< 3.0.0) #1618

Closed
soundasleep opened this issue Oct 9, 2018 · 1 comment · Fixed by jeremyrajan/vscode-exts#46 · May be fixed by bizoton19/hdwih-hugo-cms#4
Closed

Reported vulnerability in dependency randomatic (< 3.0.0) #1618

soundasleep opened this issue Oct 9, 2018 · 1 comment · Fixed by jeremyrajan/vscode-exts#46 · May be fixed by bizoton19/hdwih-hugo-cms#4

Comments

@soundasleep
Copy link

NVD has issued https://nvd.nist.gov/vuln/detail/CVE-2017-16028 which captures one of browser-syncs' sub-dependencies: randomatic (1.1.7).

$ npm ls randomatic
my-package@0.1.0 /Users/jevon/workspace/my-package
└─┬ browser-sync@2.26.0
  └─┬ micromatch@2.3.11
    └─┬ braces@1.8.5
      └─┬ expand-range@1.8.2
        └─┬ fill-range@2.2.3
          └── randomatic@1.1.7

I'm not sure if you need to update your dependencies, or if the CVE itself needs to be fixed, but as it stands I think any project using browser-sync will fail npm audit.

See also: jonschlinkert/randomatic#15

@shakyShane
Copy link
Contributor

@soundasleep hopefully 2.26.2 solves this (although I couldn't actually get npm audit to fail for me)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants