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] Upgrade next-auth from 4.23.1 to 4.23.2 #432

Closed

Conversation

mdshamoon
Copy link
Contributor

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


Snyk has created this PR to upgrade next-auth from 4.23.1 to 4.23.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 23 days ago, on 2023-10-02.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Regular Expression Denial of Service (ReDoS)
SNYK-JS-ZOD-5925617
696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Proof of Concept
Improper Input Validation
SNYK-JS-POSTCSS-5926692
696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
No Known Exploit

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


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade next-auth from 4.23.1 to 4.23.2.

See this package in npm:


See this project in Snyk:
https://app.snyk.io/org/mdshamoon/project/c884e92c-5d56-4d83-bfe3-09f785b8b3bb?utm_source=github&utm_medium=referral&page=upgrade-pr
@fatchat fatchat closed this Nov 7, 2023
@fatchat fatchat deleted the snyk-upgrade-d58e376170d3ee8a0086feac2c4e9d6e branch November 7, 2023 05:27
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.

3 participants