next-auth@4.10.0 vulnerabilities
Authentication for Next.js
-
latest version
4.24.10
-
latest non vulnerable version
-
first published
7 years ago
-
latest version published
a month ago
-
licenses detected
- >=0
Direct Vulnerabilities
Known vulnerabilities in the next-auth package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
next-auth is an Authentication for Next.js Affected versions of this package are vulnerable to Improper Authorization by obtaining an issued JWT from an interrupted OAuth sign-in flow. An attacker can manually override the Notes:
How to fix Improper Authorization? Upgrade |
<4.24.5
|
next-auth is an Authentication for Next.js Affected versions of this package are vulnerable to Session Fixation such that a bad actor who can read traffic on the victim's network or who is able to social engineer the victim to click a manipulated login link could intercept and tamper with the authorization URL to log in as the victim. How to fix Session Fixation? Upgrade |
<4.20.1
|
next-auth is an Authentication for Next.js Affected versions of this package are vulnerable to Improper Authentication due to missing validation for both the identifier and the token in the How to fix Improper Authentication? Upgrade |
<4.12.0
|
next-auth is an Authentication for Next.js Affected versions of this package are vulnerable to Improper Authorization in How to fix Improper Authorization? Upgrade |
<3.29.10
>=4.10.0 <4.10.3
|
next-auth is an Authentication for Next.js Affected versions of this package are vulnerable to Information Exposure where it is possible to reveal sensitive information such as an identity provider's secret in logs. Note: This vulnerability can be worked around by configuring the logger manually to remove the provider secret.
How to fix Information Exposure? Upgrade |
<3.29.9
>=4.0.0 <4.10.2
|