chore(deps): update dependency next-auth to v4.24.5 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-auth (source)	4.23.2 → 4.24.5

---

Possible user mocking that bypasses basic authentication

CVE-2023-48309 / GHSA-v64w-49xw-qq89

More information

Details

Impact

next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.

A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).

Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).

This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)

This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).

Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.

Patches

We patched the vulnerability in next-authv4.24.5. To upgrade, run one of the following:

npm i next-auth@latest

yarn add next-auth@latest

pnpm add next-auth@latest

Workarounds

Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:

// middleware.tsimport{withAuth}from"next-auth/middleware"exportdefaultwithAuth(/*your middleware function*/,{// checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerabilitycallbacks: {authorized: ({ token })=>!!token?.email}})

References

• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

• https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89
• https://nvd.nist.gov/vuln/detail/CVE-2023-48309
• https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10
• https://authjs.dev/guides/basics/role-based-access-control
• https://next-auth.js.org/configuration/nextjs#advanced-usage
• https://next-auth.js.org/configuration/nextjs#middlewar
• https://github.com/advisories/GHSA-v64w-49xw-qq89

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next-auth@​4.24.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@asyncapi/generator@1.13.1 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm jiti is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/cz-conventional-changelog@3.3.0 → npm/jiti@2.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jiti@2.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm rollup is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/rollup-plugin-url@3.0.1 → npm/@svgr/rollup@8.1.0 → npm/vite-plugin-dts@2.3.0 → npm/@rollup/plugin-url@7.0.0 → npm/rollup@2.80.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@2.80.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@nx-plus/docusaurus@15.0.0-rc.0 → npm/@nx/devkit@16.7.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

LGTM 👍

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-auth (source)	4.23.2 → 4.24.5

---

Possible user mocking that bypasses basic authentication

CVE-2023-48309 / GHSA-v64w-49xw-qq89

More information

Details

Impact

next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.

A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).

Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).

This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)

This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).

Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.

Patches

We patched the vulnerability in next-authv4.24.5. To upgrade, run one of the following:

npm i next-auth@latest

yarn add next-auth@latest

pnpm add next-auth@latest

Workarounds

Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:

// middleware.tsimport{withAuth}from"next-auth/middleware"exportdefaultwithAuth(/*your middleware function*/,{// checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerabilitycallbacks: {authorized: ({ token })=>!!token?.email}})

References

• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

• https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89
• https://nvd.nist.gov/vuln/detail/CVE-2023-48309
• https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10
• https://authjs.dev/guides/basics/role-based-access-control
• https://next-auth.js.org/configuration/nextjs#advanced-usage
• https://next-auth.js.org/configuration/nextjs#middlewar
• https://github.com/advisories/GHSA-v64w-49xw-qq89

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next-auth@​4.24.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@asyncapi/generator@1.13.1 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm jiti is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/cz-conventional-changelog@3.3.0 → npm/jiti@2.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jiti@2.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm rollup is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/rollup-plugin-url@3.0.1 → npm/@svgr/rollup@8.1.0 → npm/vite-plugin-dts@2.3.0 → npm/@rollup/plugin-url@7.0.0 → npm/rollup@2.80.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@2.80.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@nx-plus/docusaurus@15.0.0-rc.0 → npm/@nx/devkit@16.7.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

LGTM 👍

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-auth (source)	4.23.2 → 4.24.5

---

Possible user mocking that bypasses basic authentication

CVE-2023-48309 / GHSA-v64w-49xw-qq89

More information

Details

Impact

next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.

A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).

Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).

This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)

This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).

Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.

Patches

We patched the vulnerability in next-authv4.24.5. To upgrade, run one of the following:

npm i next-auth@latest

yarn add next-auth@latest

pnpm add next-auth@latest

Workarounds

Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:

// middleware.tsimport{withAuth}from"next-auth/middleware"exportdefaultwithAuth(/*your middleware function*/,{// checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerabilitycallbacks: {authorized: ({ token })=>!!token?.email}})

References

• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

• https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89
• https://nvd.nist.gov/vuln/detail/CVE-2023-48309
• https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10
• https://authjs.dev/guides/basics/role-based-access-control
• https://next-auth.js.org/configuration/nextjs#advanced-usage
• https://next-auth.js.org/configuration/nextjs#middlewar
• https://github.com/advisories/GHSA-v64w-49xw-qq89

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next-auth@​4.24.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@asyncapi/generator@1.13.1 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm jiti is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/cz-conventional-changelog@3.3.0 → npm/jiti@2.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jiti@2.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm rollup is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/rollup-plugin-url@3.0.1 → npm/@svgr/rollup@8.1.0 → npm/vite-plugin-dts@2.3.0 → npm/@rollup/plugin-url@7.0.0 → npm/rollup@2.80.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@2.80.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@nx-plus/docusaurus@15.0.0-rc.0 → npm/@nx/devkit@16.7.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

LGTM 👍

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-auth (source)	4.23.2 → 4.24.5

---

Possible user mocking that bypasses basic authentication

CVE-2023-48309 / GHSA-v64w-49xw-qq89

More information

Details

Impact

next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.

A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).

Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).

This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)

This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).

Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.

Patches

We patched the vulnerability in next-authv4.24.5. To upgrade, run one of the following:

npm i next-auth@latest

yarn add next-auth@latest

pnpm add next-auth@latest

Workarounds

Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:

// middleware.tsimport{withAuth}from"next-auth/middleware"exportdefaultwithAuth(/*your middleware function*/,{// checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerabilitycallbacks: {authorized: ({ token })=>!!token?.email}})

References

• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

• https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89
• https://nvd.nist.gov/vuln/detail/CVE-2023-48309
• https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10
• https://authjs.dev/guides/basics/role-based-access-control
• https://next-auth.js.org/configuration/nextjs#advanced-usage
• https://next-auth.js.org/configuration/nextjs#middlewar
• https://github.com/advisories/GHSA-v64w-49xw-qq89

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next-auth@​4.24.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@asyncapi/generator@1.13.1 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm jiti is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/cz-conventional-changelog@3.3.0 → npm/jiti@2.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jiti@2.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm rollup is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/rollup-plugin-url@3.0.1 → npm/@svgr/rollup@8.1.0 → npm/vite-plugin-dts@2.3.0 → npm/@rollup/plugin-url@7.0.0 → npm/rollup@2.80.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@2.80.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@nx-plus/docusaurus@15.0.0-rc.0 → npm/@nx/devkit@16.7.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

LGTM 👍

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-auth (source)	4.23.2 → 4.24.5

---

Possible user mocking that bypasses basic authentication

CVE-2023-48309 / GHSA-v64w-49xw-qq89

More information

Details

Impact

next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.

A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).

Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).

This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)

This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).

Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.

Patches

We patched the vulnerability in next-authv4.24.5. To upgrade, run one of the following:

npm i next-auth@latest

yarn add next-auth@latest

pnpm add next-auth@latest

Workarounds

Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:

// middleware.tsimport{withAuth}from"next-auth/middleware"exportdefaultwithAuth(/*your middleware function*/,{// checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerabilitycallbacks: {authorized: ({ token })=>!!token?.email}})

References

• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

• https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89
• https://nvd.nist.gov/vuln/detail/CVE-2023-48309
• https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10
• https://authjs.dev/guides/basics/role-based-access-control
• https://next-auth.js.org/configuration/nextjs#advanced-usage
• https://next-auth.js.org/configuration/nextjs#middlewar
• https://github.com/advisories/GHSA-v64w-49xw-qq89

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next-auth@​4.24.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@asyncapi/generator@1.13.1 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm jiti is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/cz-conventional-changelog@3.3.0 → npm/jiti@2.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jiti@2.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm rollup is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/rollup-plugin-url@3.0.1 → npm/@svgr/rollup@8.1.0 → npm/vite-plugin-dts@2.3.0 → npm/@rollup/plugin-url@7.0.0 → npm/rollup@2.80.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@2.80.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@nx-plus/docusaurus@15.0.0-rc.0 → npm/@nx/devkit@16.7.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

LGTM 👍

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-auth (source)	4.23.2 → 4.24.5

---

Possible user mocking that bypasses basic authentication

CVE-2023-48309 / GHSA-v64w-49xw-qq89

More information

Details

Impact

next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.

A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).

Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).

This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)

This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).

Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.

Patches

We patched the vulnerability in next-authv4.24.5. To upgrade, run one of the following:

npm i next-auth@latest

yarn add next-auth@latest

pnpm add next-auth@latest

Workarounds

Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:

// middleware.tsimport{withAuth}from"next-auth/middleware"exportdefaultwithAuth(/*your middleware function*/,{// checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerabilitycallbacks: {authorized: ({ token })=>!!token?.email}})

References

• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

• https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89
• https://nvd.nist.gov/vuln/detail/CVE-2023-48309
• https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10
• https://authjs.dev/guides/basics/role-based-access-control
• https://next-auth.js.org/configuration/nextjs#advanced-usage
• https://next-auth.js.org/configuration/nextjs#middlewar
• https://github.com/advisories/GHSA-v64w-49xw-qq89

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next-auth@​4.24.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@asyncapi/generator@1.13.1 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm jiti is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/cz-conventional-changelog@3.3.0 → npm/jiti@2.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jiti@2.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm rollup is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/rollup-plugin-url@3.0.1 → npm/@svgr/rollup@8.1.0 → npm/vite-plugin-dts@2.3.0 → npm/@rollup/plugin-url@7.0.0 → npm/rollup@2.80.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@2.80.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@nx-plus/docusaurus@15.0.0-rc.0 → npm/@nx/devkit@16.7.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

LGTM 👍

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-auth (source)	4.23.2 → 4.24.5

---

Possible user mocking that bypasses basic authentication

CVE-2023-48309 / GHSA-v64w-49xw-qq89

More information

Details

Impact

next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.

A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).

Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).

This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)

This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).

Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.

Patches

We patched the vulnerability in next-authv4.24.5. To upgrade, run one of the following:

npm i next-auth@latest

yarn add next-auth@latest

pnpm add next-auth@latest

Workarounds

Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:

// middleware.tsimport{withAuth}from"next-auth/middleware"exportdefaultwithAuth(/*your middleware function*/,{// checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerabilitycallbacks: {authorized: ({ token })=>!!token?.email}})

References

• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

• https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89
• https://nvd.nist.gov/vuln/detail/CVE-2023-48309
• https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10
• https://authjs.dev/guides/basics/role-based-access-control
• https://next-auth.js.org/configuration/nextjs#advanced-usage
• https://next-auth.js.org/configuration/nextjs#middlewar
• https://github.com/advisories/GHSA-v64w-49xw-qq89

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next-auth@​4.24.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@asyncapi/generator@1.13.1 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm jiti is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/cz-conventional-changelog@3.3.0 → npm/jiti@2.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jiti@2.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm rollup is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/rollup-plugin-url@3.0.1 → npm/@svgr/rollup@8.1.0 → npm/vite-plugin-dts@2.3.0 → npm/@rollup/plugin-url@7.0.0 → npm/rollup@2.80.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@2.80.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@nx-plus/docusaurus@15.0.0-rc.0 → npm/@nx/devkit@16.7.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

LGTM 👍

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
next-auth (source)	4.23.2 → 4.24.5

---

Possible user mocking that bypasses basic authentication

CVE-2023-48309 / GHSA-v64w-49xw-qq89

More information

Details

Impact

next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.

A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).

Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).

This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)

This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).

Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.

Patches

We patched the vulnerability in next-authv4.24.5. To upgrade, run one of the following:

npm i next-auth@latest

yarn add next-auth@latest

pnpm add next-auth@latest

Workarounds

Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:

// middleware.tsimport{withAuth}from"next-auth/middleware"exportdefaultwithAuth(/*your middleware function*/,{// checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerabilitycallbacks: {authorized: ({ token })=>!!token?.email}})

References

• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

• https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89
• https://nvd.nist.gov/vuln/detail/CVE-2023-48309
• https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10
• https://authjs.dev/guides/basics/role-based-access-control
• https://next-auth.js.org/configuration/nextjs#advanced-usage
• https://next-auth.js.org/configuration/nextjs#middlewar
• https://github.com/advisories/GHSA-v64w-49xw-qq89

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

Code review by ChatGPT

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[github-actions]

LGTM 👍

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next-auth@​4.24.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@asyncapi/generator@1.13.1 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm jiti is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/cz-conventional-changelog@3.3.0 → npm/jiti@2.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/jiti@2.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm rollup is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/rollup-plugin-url@3.0.1 → npm/@svgr/rollup@8.1.0 → npm/vite-plugin-dts@2.3.0 → npm/@rollup/plugin-url@7.0.0 → npm/rollup@2.80.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@2.80.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/@nx-plus/docusaurus@15.0.0-rc.0 → npm/@nx/devkit@16.7.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

LGTM 👍