-
Notifications
You must be signed in to change notification settings - Fork 64
feat: fs x #2795
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
base: main
Are you sure you want to change the base?
feat: fs x #2795
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
return NextResponse.json({ | ||
status: 200, | ||
revalidated: false, | ||
now: Date.now(), | ||
message: 'Missing path to revalidate', | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Risk: Affected versions of next are vulnerable to Improper Authorization. Improper authorization handling in Next.js applications enables attackers to bypass security controls for paths directly under the application's root directory, potentially exposing sensitive data or functionality. This issue affects versions prior to Next.js 14.2.15, where authorization logic based solely on pathname fails to account for certain direct page accesses.
Manual Review Advice: A vulnerability from this advisory is reachable if you use authorization to protect a page directly under the application's root directory (for example, https://example.com/foo) and you do NOT host your application on Vercel
Fix: Upgrade this library to at least version 14.2.15 at faststore/pnpm-lock.yaml:7944.
Reference(s): GHSA-7gfc-8cq8-jh5f, CVE-2024-51479
🎈 Fixed in commit 67906b0 🎈
|
||
revalidatePath(path, 'page') | ||
|
||
return NextResponse.json({ status: 200, revalidated: true, now: Date.now() }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Risk: Affected versions of next are vulnerable to Improper Authorization. Next.js middleware-based authorization checks can be bypassed by an attacker who forges external requests that include a specific header, tricking the application into treating the request as a trusted internal call and thus bypassing access controls.
Manual Review Advice: A vulnerability from this advisory is reachable if you perform authorization in the middleware
Fix: Upgrade this library to at least version 15.2.3 at faststore/pnpm-lock.yaml:7843.
Reference(s): GHSA-f82v-jwr5-mffw, CVE-2025-29927
🎉 Removed in commit 3f17bfb 🎉
return NextResponse.json({ | ||
status: 200, | ||
revalidated: false, | ||
now: Date.now(), | ||
message: 'Missing path to revalidate', | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Risk: Affected versions of next are vulnerable to Improper Authorization. Next.js middleware-based authorization checks can be bypassed by an attacker who forges external requests that include a specific header, tricking the application into treating the request as a trusted internal call and thus bypassing access controls.
Manual Review Advice: A vulnerability from this advisory is reachable if you perform authorization in the middleware
Fix: Upgrade this library to at least version 15.2.3 at faststore/pnpm-lock.yaml:7843.
Reference(s): GHSA-f82v-jwr5-mffw, CVE-2025-29927
🧼 Removed in commit 3f17bfb 🧼
|
||
revalidatePath(path, 'page') | ||
|
||
return NextResponse.json({ status: 200, revalidated: true, now: Date.now() }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Risk: Affected versions of next are vulnerable to Improper Authorization. Improper authorization handling in Next.js applications enables attackers to bypass security controls for paths directly under the application's root directory, potentially exposing sensitive data or functionality. This issue affects versions prior to Next.js 14.2.15, where authorization logic based solely on pathname fails to account for certain direct page accesses.
Manual Review Advice: A vulnerability from this advisory is reachable if you use authorization to protect a page directly under the application's root directory (for example, https://example.com/foo) and you do NOT host your application on Vercel
Fix: Upgrade this library to at least version 14.2.15 at faststore/pnpm-lock.yaml:7944.
Reference(s): GHSA-7gfc-8cq8-jh5f, CVE-2024-51479
✨ Fixed in commit 67906b0 ✨
return NextResponse.json({ | ||
status: 200, | ||
revalidated: true, | ||
now: Date.now(), | ||
message: `Revalidated path: ${path}`, | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Risk: Affected versions of next are vulnerable to Improper Authorization. Next.js middleware-based authorization checks can be bypassed by an attacker who forges external requests that include a specific header, tricking the application into treating the request as a trusted internal call and thus bypassing access controls.
Manual Review Advice: A vulnerability from this advisory is reachable if you perform authorization in the middleware
Fix: Upgrade this library to at least version 15.2.3 at faststore/pnpm-lock.yaml:7843.
Reference(s): GHSA-f82v-jwr5-mffw, CVE-2025-29927
💬 To ignore this, reply with:
• /fp <comment>
for false positive
• /ar <comment>
for acceptable risk
• /other <comment>
for all other reasons
Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by ssc-91c0a03f-a79a-4539-915f-c718686fa6b7.
return NextResponse.json({ | ||
status: 200, | ||
revalidated: false, | ||
now: Date.now(), | ||
message: 'Missing path to revalidate', | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Risk: Affected versions of next are vulnerable to Improper Authorization. Next.js middleware-based authorization checks can be bypassed by an attacker who forges external requests that include a specific header, tricking the application into treating the request as a trusted internal call and thus bypassing access controls.
Manual Review Advice: A vulnerability from this advisory is reachable if you perform authorization in the middleware
Fix: Upgrade this library to at least version 15.2.3 at faststore/pnpm-lock.yaml:7843.
Reference(s): GHSA-f82v-jwr5-mffw, CVE-2025-29927
💬 To ignore this, reply with:
• /fp <comment>
for false positive
• /ar <comment>
for acceptable risk
• /other <comment>
for all other reasons
Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by ssc-91c0a03f-a79a-4539-915f-c718686fa6b7.
[WIP]
Changeset: