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] Fix for 10 vulnerabilities #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
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
    • package-lock.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
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-JS-AXIOS-174505
No No Known Exploit
high severity 590/1000
Why? Has a fix available, CVSS 7.3
Insecure Randomness
SNYK-JS-CRYPTOJS-548472
No No Known Exploit
medium severity 636/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
Prototype Pollution
SNYK-JS-DOTPROP-543489
Yes Proof of Concept
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
Signature Validation Bypass
SNYK-JS-ELECTRONUPDATER-561421
Yes No Known Exploit
medium severity 459/1000
Why? Has a fix available, CVSS 4.9
Buffer Overflow
SNYK-JS-I18NEXT-575536
Yes No Known Exploit
medium severity 561/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 4.8
Prototype Pollution
SNYK-JS-I18NEXT-585930
Yes Proof of Concept
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-JS-JSYAML-173999
No No Known Exploit
high severity 619/1000
Why? Has a fix available, CVSS 8.1
Arbitrary Code Execution
SNYK-JS-JSYAML-174129
No No Known Exploit
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
Cross-site Scripting (XSS)
SNYK-JS-PUPA-174563
Yes No Known Exploit

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

Commit messages
Package name: axios The new version differs by 14 commits.

See the full diff

Package name: electron-context-menu The new version differs by 41 commits.

See the full diff

Package name: electron-store The new version differs by 9 commits.

See the full diff

Package name: i18next The new version differs by 250 commits.
  • 8c63160 19.6.0
  • 2a6d7e7 changelog
  • 26d5719 introduce new option skipOnVariables to fix #1479 (#1483)
  • 44c2e76 fix prototype pollution (#1482)
  • 8a3b93b 19.5.6
  • 1b32fc1 fix local usage of nsSeparator option
  • c9be7ad 19.5.5
  • 41431ba changelog
  • 360c8a9 fix nesting recursion #1479 (#1480)
  • 2108da8 additional interpolation with nesting test case
  • 457768b 19.5.4
  • 93f17d9 changelog
  • 9be2ed6 fix type declarion of exposed EventEmitter#off methods (#1460)
  • c883ddb fix: getDataByLanguage typings & test (#1472)
  • 4bfa7a3 19.5.3
  • 39b09ed changelog
  • e3ad1ad fix: Macedonian plural formula - *11 (11, 111, 211, 311, 58711...) is plural (#1476)
  • 72c5009 19.5.2
  • 6dc82bb changelog
  • 1b78398 fix nesting interpolation with prepended namespace, fixes #1474 (#1475)
  • 67e2569 19.5.1
  • 0e1ba26 rebuild
  • 80a3810 Merge pull request #1471 from i18next/fix-getBestMatchFromCodes
  • ba5c120 getBestMatchFromCodes: use fallbackLng if nothing found, fixes #1470

See the full diff

Package name: redux-persist-electron-storage The new version differs by 21 commits.

See the full diff

With a Snyk patch:
Severity Priority Score (*) Issue Exploit Maturity
medium severity 636/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
Prototype Pollution
SNYK-JS-LODASH-567746
Proof of Concept

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