Open redirect via encoded static error-page paths
Published Aug 11, 2021 · Updated Aug 4, 2024
Open redirect in Next.js 10.0.5 through 10.2.0 and 11.0.0 through 11.0.1 allows remote attackers to redirect users via encoded paths. The statically generated pages/_error.js route improperly parses specially encoded request paths beginning with a double slash and domain as an external redirect target. Exposure requires an affected error-page configuration; Vercel deployments and applications with pages/404.js are unaffected, and phishing requires a user to follow the crafted link.
Summary
What happened
Open redirect in Next.js 10.0.5 through 10.2.0 and 11.0.0 through 11.0.1 allows remote attackers to redirect users via encoded paths. The statically generated pages/_error.js route improperly parses specially encoded request paths beginning with a double slash and domain as an external redirect target. Exposure requires an affected error-page configuration; Vercel deployments and applications with pages/404.js are unaffected, and phishing requires a user to follow the crafted link.
The record
- CVE
- CVE-2021-37699
- Published
- Aug 11, 2021
- Updated
- Aug 4, 2024
- Vendor
- Vercel
- Product
- Next.js
- Classifications
- CWE-601, T1566.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 11.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo