Next.js versions before 9.3.2 have a directory traversal vulnerability. Attackers could craft special requests to access files in the dist directory (.next). This does not affect files outside of the dist directory (.next). In general, the dist directory only holds build assets u...
Vendor
zeit vulnerabilities
9 published CVES affecting zeit, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 9
- Critical
- 0
- High
- 4
- Medium
- 5
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest zeit CVEs
Newest publication first
-
MediumCVSS 4.3 EPSS 44.8%
-
CVE-2019-5415 Path Traversal in serve
PublishedHighCVSS 7.5 EPSS 1.6%A bug in handling the ignore files and directories feature in serve 6.5.3 allows an attacker to read a file or list the directory that the victim has not allowed access to.
-
HighCVSS 7.5 EPSS 2.3%
A path traversal vulnerability in serve npm package version 7.0.1 allows the attackers to read content of arbitrary files on the remote server.
-
CVE-2018-18282 Next.js has cross site scripting (XSS) vulnerability via the 404 or 500 /_error page
PublishedMediumCVSS 6.1 EPSS 1.0%Next.js 7.0.0 and 7.0.1 has XSS via the 404 or 500 /_error page.
-
MediumCVSS 5.3 EPSS 1.3%
serve node module suffers from Improper Handling of URL Encoding by permitting access to ignored files if a filename is URL encoded.
-
MediumCVSS 6.5 EPSS 1.8%
serve node module before 6.4.9 suffers from a Path Traversal vulnerability due to not handling %2e (.) and %2f (/) and allowing them in paths, which allows a malicious user to view the contents of any directory with known path.
-
MediumCVSS 5.3 EPSS 1.0%
Information exposure through directory listings in serve 6.5.3 allows directory listing and file access even when they have been set to be ignored.
-
HighCVSS 7.5 EPSS 9.1%
ZEIT Next.js 4 before 4.2.3 has Directory Traversal under the /_next request namespace.
-
HighCVSS 7.5 EPSS 14.1%
ZEIT Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.