Skip to content

Conversation

@parseplatformorg
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 671/1000
Why? Recently disclosed, Has a fix available, CVSS 7.7
Improper Input Validation
SNYK-JS-JSONWEBTOKEN-3180020
Yes No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Improper Authentication
SNYK-JS-JSONWEBTOKEN-3180022
Yes No Known Exploit
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5
Improper Restriction of Security Token Assignment
SNYK-JS-JSONWEBTOKEN-3180024
Yes No Known Exploit
medium severity 526/1000
Why? Recently disclosed, Has a fix available, CVSS 4.8
Use of a Broken or Risky Cryptographic Algorithm
SNYK-JS-JSONWEBTOKEN-3180026
Yes No Known Exploit

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

Commit messages
Package name: jsonwebtoken The new version differs by 17 commits.

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:

🦉 Use of a Broken or Risky Cryptographic Algorithm

@parse-github-assistant
Copy link

Thanks for opening this pull request!

  • ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.

@codecov
Copy link

codecov bot commented Dec 22, 2022

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.42%. Comparing base (650993d) to head (c5a21a6).
Report is 34 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #123   +/-   ##
=======================================
  Coverage   93.42%   93.42%           
=======================================
  Files          23       23           
  Lines         578      578           
=======================================
  Hits          540      540           
  Misses         38       38           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@VulchiSarath
Copy link

When can we expect these fixes because [email protected] as high vulnerable and I hope fixes also ready. It will be helpful if you guys release these fixes asap.

@ldikmans
Copy link

It would be very helpful if this could be fixed

@ldikmans
Copy link

ldikmans commented Mar 13, 2023

@mtrezza do you know if anyone is still maintaining this library? This library is also used in node-pushnotifications, see package.json

This security upgrade would be very helpful. Thanks for your reply!

@mtrezza
Copy link
Member

mtrezza commented Mar 14, 2023

Our fork contains a few changes that are partly also merged in the original repository. The current intention is to compare the 2, bring the original repo up-to-date (if needed at all), then archive our fork and use the original repo instead. There have been similar PRs merged on both and releases published on both, so this take a bit more effort.

@ldikmans
Copy link

Our fork contains a few changes that are partly also merged in the original repository. The current intention is to compare the 2, bring the original repo up-to-date (if needed at all), then archive our fork and use the original repo instead. There have been similar PRs merged on both and releases published on both, so this take a bit more effort.

Would it be possible to merge the fix in the mean time?

@cbaker6
Copy link

cbaker6 commented Feb 8, 2025

@mtrezza this can be closed, handled in #159

@mtrezza mtrezza closed this Feb 8, 2025
@mtrezza mtrezza deleted the snyk-fix-042af70cafdbde7b20d1d36feadb8bd2 branch February 8, 2025 19:40
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.

7 participants