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

[Snyk] Fix for 14 vulnerabilities #5

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

Conversation

MarcelRaschke
Copy link
Collaborator

This PR was automatically created by Snyk using the credentials of a real user.


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.

⚠️ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 584/1000
Why? Has a fix available, CVSS 7.4
Directory Traversal
SNYK-JS-ADMZIP-1065796
No No Known Exploit
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIREGEX-1583908
Yes Proof of Concept
high severity 869/1000
Why? Mature exploit, Has a fix available, CVSS 8.8
Use After Free
SNYK-JS-ELECTRON-174045
No Mature
high severity 624/1000
Why? Has a fix available, CVSS 8.2
Arbitrary Code Execution
SNYK-JS-ELECTRON-483050
No No Known Exploit
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-JS-WS-1296835
No Proof of Concept
medium severity 601/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
Prototype Pollution
SNYK-JS-YARGSPARSER-560381
Yes Proof of Concept
critical severity 899/1000
Why? Mature exploit, Has a fix available, CVSS 9.4
Arbitrary File Write via Archive Extraction (Zip Slip)
npm:adm-zip:20180415
No Mature
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Regular Expression Denial of Service (ReDoS)
npm:braces:20180219
No Proof of Concept
medium severity 469/1000
Why? Has a fix available, CVSS 5.1
Denial of Service (DoS)
npm:mem:20180117
Yes No Known Exploit

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

Commit messages
Package name: all-contributors-cli The new version differs by 50 commits.

See the full diff

Package name: lint-staged The new version differs by 250 commits.

See the full diff

Package name: nightmare The new version differs by 5 commits.
  • af11432 Release 3.0.2
  • 0bcd8f8 Merge pull request #1534 from julianladisch/Chromium-FileReader-Vulnerability
  • 98c842f Electron 2.0.18 - Chromium FileReader Vulnerability Fix (CVE-2019-5786)
  • 0d76929 feat: Adds support for custom user agents.
  • 0bd6dbc bumps the version of electron to 2.0.2

See the full diff

With a Snyk patch:
Severity Priority Score (*) Issue Exploit Maturity
high severity 731/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 8.2
Prototype Pollution
SNYK-JS-LODASH-567746
Proof of Concept
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Regular Expression Denial of Service (ReDoS)
npm:debug:20170905
No Known Exploit
high severity 579/1000
Why? Has a fix available, CVSS 7.3
Prototype Pollution
npm:extend:20180424
No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Regular Expression Denial of Service (ReDoS)
npm:ms:20170412
No Known Exploit
medium severity 646/1000
Why? Mature exploit, Has a fix available, CVSS 5.2
Uninitialized Memory Exposure
npm:stringstream:20180511
Mature

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

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


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Directory Traversal
🦉 Prototype Pollution

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

Successfully merging this pull request may close these issues.

2 participants