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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade crypto-js from 3.3.0 to 4.0.0 #9

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

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented May 7, 2021

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

merge advice

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 590/1000
Why? Has a fix available, CVSS 7.3
Insecure Randomness
SNYK-JS-CRYPTOJS-548472
Yes No Known Exploit

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

Commit messages
Package name: crypto-js The new version differs by 7 commits.
  • 31d0012 Merge branch 'release/4.0.0'
  • ba08310 Add release notes.
  • 38b74c0 Bump major reslease version.
  • 1d30318 Pull `3.3.0` from `master` into `develop`.
  • fc90e5a Reverse the rollback to head on with a 4.x.x version.
  • b60b80c Add test page which uses the created bundle after build to run the tests.
  • 61b6a4e Merge branch 'release/3.2.1' into develop

See the full diff

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
Labels
None yet
Projects
None yet
1 participant