[GHSA-f82v-jwr5-mffw] Authorization Bypass in Next.js Middleware#6431
[GHSA-f82v-jwr5-mffw] Authorization Bypass in Next.js Middleware#6431Jinz426 wants to merge 1 commit intoJinz426/advisory-improvement-6431from
Conversation
There was a problem hiding this comment.
Pull Request Overview
This pull request attempts to update the security advisory for CVE-2025-29927, an authorization bypass vulnerability in Next.js middleware, by upgrading the CVSS scoring from v3.1 to v4.0 and updating the severity rating. However, the changes introduce critical errors that significantly misrepresent the vulnerability's severity.
Key Changes:
- Updated CVSS scoring from v3.1 to v4.0
- Downgraded severity from CRITICAL to LOW
- Updated the modified timestamp
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "type": "CVSS_V3", | ||
| "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N" | ||
| "type": "CVSS_V4", | ||
| "score": "CVSS:4.0/AV:P/AC:H/AT:P/PR:H/UI:A/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N" |
There was a problem hiding this comment.
The CVSS v4.0 score is severely incorrect and misrepresents the vulnerability severity. The new score indicates:
- Physical access required (AV:P) when this is a network-based vulnerability
- No impact on confidentiality, integrity, or availability (all metrics set to N) when this is an authorization bypass with high impact
- High privileges required (PR:H) when the original correctly identified this requires no privileges
This vulnerability allows bypassing authorization checks via network requests with a specific header. The original CVSS v3.1 score (9.1 CRITICAL) correctly reflected this. The new score would rate near 0.0, which is completely inconsistent with the vulnerability description stating it "is possible to bypass authorization checks."
The CVSS v4.0 score should maintain high impact ratings for confidentiality and integrity, network attack vector, and low/no privilege requirements to accurately represent this authorization bypass vulnerability.
| "score": "CVSS:4.0/AV:P/AC:H/AT:P/PR:H/UI:A/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N" | |
| "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/S:U/SC:N/SI:N/SA:N" |
| "CWE-863" | ||
| ], | ||
| "severity": "CRITICAL", | ||
| "severity": "LOW", |
There was a problem hiding this comment.
The severity downgrade from "CRITICAL" to "LOW" is incorrect and inconsistent with the vulnerability description. This is an authorization bypass vulnerability that allows external users to bypass authorization checks in Next.js middleware by adding a specific header to their requests. Such vulnerabilities typically warrant CRITICAL or HIGH severity ratings due to their potential for unauthorized access to protected resources.
The severity should remain "CRITICAL" (or at minimum "HIGH") to match the actual risk posed by this authorization bypass vulnerability. A "LOW" severity rating significantly understates the security risk and could lead to delayed patching by affected users.
| "severity": "LOW", | |
| "severity": "CRITICAL", |
Updates
Comments
automise upgrade for security system