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] Security upgrade log4js from 2.5.3 to 6.4.0 #14

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

Conversation

marco-panepinto
Copy link

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
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 619/1000
Why? Has a fix available, CVSS 8.1
Prototype Pollution
SNYK-JS-AJV-584908
Yes No Known Exploit
high severity 584/1000
Why? Has a fix available, CVSS 7.4
Regular Expression Denial of Service (ReDoS)
SNYK-JS-HAWK-2808852
Yes 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-ISMYJSONVALID-597165
Yes Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Arbitrary Code Execution
SNYK-JS-ISMYJSONVALID-597167
Yes Proof of Concept
medium severity 601/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
Prototype Pollution
SNYK-JS-JSONPOINTER-1577288
Yes Proof of Concept
critical severity 811/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9.8
Prototype Pollution
SNYK-JS-JSONPOINTER-598804
Yes Proof of Concept
high severity 644/1000
Why? Has a fix available, CVSS 8.6
Prototype Pollution
SNYK-JS-JSONSCHEMA-1920922
Yes 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-LODASH-1018905
Yes Proof of Concept
high severity 681/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.2
Command Injection
SNYK-JS-LODASH-1040724
Yes Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution
SNYK-JS-LODASH-450202
Yes Proof of Concept
high severity 731/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 8.2
Prototype Pollution
SNYK-JS-LODASH-567746
Yes Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution
SNYK-JS-LODASH-608086
Yes Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution
SNYK-JS-LODASH-73638
Yes Proof of Concept
medium severity 541/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 4.4
Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-73639
Yes Proof of Concept
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Prototype Pollution
SNYK-JS-MINIMIST-2429795
Yes Proof of Concept
medium severity 601/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
Prototype Pollution
SNYK-JS-MINIMIST-559764
Yes Proof of Concept
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Prototype Poisoning
SNYK-JS-QS-3153490
Yes Proof of Concept
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
Yes Proof of Concept
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Insecure Randomness
npm:cryptiles:20180710
Yes No Known Exploit
high severity 579/1000
Why? Has a fix available, CVSS 7.3
Prototype Pollution
npm:extend:20180424
Yes No Known Exploit
medium severity 646/1000
Why? Mature exploit, Has a fix available, CVSS 5.2
Uninitialized Memory Exposure
npm:stringstream:20180511
Yes Mature

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

Commit messages
Package name: log4js The new version differs by 250 commits.
  • 9fdbed5 6.4.0
  • 788c7a8 Merge pull request #1150 from log4js-node/update-changelog
  • 7fdb141 chore: updated changelog for 6.4.0
  • e6bd888 Merge pull request #1151 from log4js-node/feat-zero-backup
  • ac599e4 allow for zero backup - in sync with https://github.com/fix: allow for zero backups and zero daysToKeep log4js-node/streamroller#74
  • 53248cd Merge pull request #1149 from log4js-node/migrate-daysToKeep-to-numBackups
  • 436d9b4 Merge pull request #1148 from log4js-node/update-docs
  • d6b017e chore(docs): updated fileSync.md and misc comments
  • d4617a7 chore(deps): migrated from daysToKeep to numBackups due to streamroller@^3.0.0
  • 0ad0133 Merge pull request #1147 from log4js-node/update-deps
  • 773962b Merge pull request #1146 from log4js-node/update-deps
  • 823bb46 Merge pull request #1145 from log4js-node/update-deps
  • 6cc0035 chore(deps): bump streamroller from 3.0.1 to 3.0.2
  • 0f39859 chore(deps): bump date-format from 4.0.2 to 4.0.3
  • 85ac31e chore(deps-dev): bump eslint from from 8.6.0 to 8.7.0
  • acd41ef Merge pull request #1144 from log4js-node/refactor
  • 4c4bbe8 chore(refactor): using writer.writable instead of alive for checking
  • e86a809 Merge pull request #1097 from 4eb0da/datefile-error-handling
  • 34ab3b2 Merge pull request #1143 from log4js-node/update-test
  • 8cba85f chore(test): renamed tap.teardown() to tap.tearDown() for consistency (while both works, only tap.tearDown() is documented)
  • a0baec2 chore(test): fixed teardown() causing tests to fail due to fs errors on removal
  • 51ac865 Merge pull request #1103 from polo-language/recording-typescript
  • 653a20f Merge pull request #1028 from techmunk/master
  • 43a2199 chore(test): Changed default TAP test suite timeout from 30s to 45s because Windows takes a long time

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


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Arbitrary Code Execution
🦉 More lessons are available in Snyk Learn

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

Successfully merging this pull request may close these issues.

2 participants