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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Fix for 5 vulnerabilities #29

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Fix for 5 vulnerabilities #29

wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

    • package.json

  • Adding or updating a Snyk policy (.snyk) file; this file is required in order to apply Snyk vulnerability patches.
    Find out more.

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 776/1000
Why? Recently disclosed, Has a fix available, CVSS 9.8		 Prototype Pollution
SNYK-JS-LODASH-590103		 Yes No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: anchor The new version differs by 39 commits.
  • 819083a 0.11.4
  • 9eae256 Bump deps
  • 2566882 0.11.3
  • 4b6d85a Update error message created in errorFactory
  • af50852 Add note about the behavior of require('validator').isNull([]) and 'required' validation checks.
  • cbbc3a5 0.11.2
  • 8c2fc2d remove one of the worse npm options i've ever seen
  • c820ad0 Code conventions.
  • e80f0dd Remove undocumented rule 'len'
  • 1a12163 0.11.1
  • 24a7761 Merge branch 'master' of github.com:balderdashy/anchor
  • 63fe5af Take errors thrown from inside of validation rules and concatenate them onto the generated default error message.
  • 0ff4c61 clean out old stuff from package.json
  • 4c37226 0.11.0
  • b294231 use break instead of return
  • c470c77 ignore validations that are set to "false"
  • 40aa514 normalize booleans
  • e7fbec2 update and lock down dependency versions
  • ee132ef update mocha version
  • 212328c normalize old files to spaces over tabs and 2 over 4
  • c42db8b cleanup whitespace
  • 11ca413 add semicolon
  • 9cdad08 fix tests
  • 9abea11 don't pass the flag value to the validations

See the full diff

Package name: grunt-contrib-coffee The new version differs by 38 commits.

See the full diff

Package name: grunt-contrib-less The new version differs by 60 commits.

See the full diff

Package name: grunt-contrib-uglify The new version differs by 49 commits.

See the full diff

Package name: grunt-sync The new version differs by 17 commits.

See the full diff

Package name: sails-disk The new version differs by 85 commits.
  • 15faa44 1.0.0
  • a2b7ee6 1.0.0-12
  • 9d7118c Only set footprint keys for uniqueness violations.
  • a2c2261 Add some assertions.
  • a222824 Update gitignore and scripts
  • 3b3c334 1.0.0-11
  • cef95b4 Support updating the primary key value, as long as it's not using _id as the column.
  • aad2a15 Set _id column to value of primary key when creating records.
  • 333e2d1 1.0.0-10
  • c8a26c5 Add shim to replicate MongoDB's behavior w/ `{ $ne: null }` and empty arrays.
  • bf92cb8 1.0.0-9
  • af97943 Workaround issue with projections including only `_id`
  • b5b985b Relax restrictions on using `_id` column in sails disk.
  • f4adfd7 Add an entry in the `refCols` dictionary for every model, so we don't have to short-circuit checks for it later
  • b494fd9 In `find`, deserialize Buffer objects into `ref` attributes where possible.
  • 7aaaaa4 Merge pull request Update command line tool w/ a few defautl policies balderdashy/sails#58 from balderdashy/expose-lib
  • 70ead96 (whoops) Add back 0.10 and 0.12 in appveyor.yml
  • beabe7a Merge pull request 403 for performing action without permission balderdashy/sails#57 from balderdashy/expose-lib
  • 9c80187 1.0.0-8
  • f7a349d Actually, don't expose the static lib. (No reason to do so, and better to not introduce something experimental if there's any chance it could make an app dependent on random stuff in a dev-only adapter)
  • 2d4d97e 1.0.0-7
  • f2dd761 Rename afterwards function to avoid perceived scope conflict (whether or not it'd ever actually be a big deal, this avoids any potential future scope issues from refactoring, etc).
  • 4051e5e 1.0.0-6
  • 250c32e Handle stray error (and a couple of other trivial changes just from when I was reading through the code)

See the full diff

Package name: sails-generate The new version differs by 250 commits.

See the full diff

Package name: waterline The new version differs by 250 commits.

See the full diff

With a Snyk patch:
Severity Priority Score (*) Issue Exploit Maturity
low severity 399/1000
Why? Has a fix available, CVSS 3.7		 Regular Expression Denial of Service (ReDoS)
npm:debug:20170905		 No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3		 Regular Expression Denial of Service (ReDoS)
npm:ms:20151024		 No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5		 Regular Expression Denial of Service (ReDoS)
npm:negotiator:20160616		 No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3		 Insecure Randomness
npm:ws:20160920		 No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Smart JSON scaffolds (for Backbone.sync) Extrapolate authentication stuff into separate plugin
1 participant
@snyk-bot