Next.js, at its very early stages, is represented by these two versions, 0.1.0 and 0.1.1, both designed as Node.js extensions. Examining these early iterations offers insight into the project's inception. Both versions share a common dependency: es5-ext version "0.5.x," ensuring compatibility with ECMAScript 5 extensions. The absence of devDependencies suggests a streamlined development and testing process at this nascent phase. They are maintained by Mariusz Nowak and come from the same repository.
The core difference between version 0.1.0 and 0.1.1 lies primarily in their release dates. There is a difference of an hour and 10 minutes between the releases, with version 0.1.1 being the later release. As a micro version update, the updates are usually represented by bug fixes or typo corrections but without more information of the library is impossible to know for sure what changed.
For developers considering using next, understanding its foundational purpose as a Node.js extension library is key. The dependency on es5-ext indicates a focus on extending the capabilities of standard JavaScript environments. While these versions are incredibly old, they lay the foundation for the modern Next.js framework. Developers interested in the historical evolution of Next.js or those working with legacy Node.js projects might find these versions relevant for study or compatibility purposes. However, modern projects should undoubtedly leverage the latest stable releases of Next.js for optimal performance and features.
All the vulnerabilities related to the version 0.1.1 of the package
Directory Traversal in Next.js
serverless targetnext exportWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
https://github.com/zeit/next.js/releases/tag/v9.3.2
https://github.com/zeit/next.js/releases/tag/v9.3.2
Next.js Race Condition to Cache Poisoning
Summary
We received a responsible disclosure from Allam Rachid (zhero) for a low-severity race-condition vulnerability in Next.js. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve pageProps data instead of standard HTML.
Credit
Thank you to Allam Rachid (zhero) for the responsible disclosure. This research was rewarded as part of our bug bounty program.
Next.js Content Injection Vulnerability for Image Optimization
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.
All users relying on images.domains or images.remotePatterns are encouraged to upgrade and verify that external image sources are strictly validated.
More details at Vercel Changelog
Next.js Improper Middleware Redirect Handling Leads to SSRF
A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into NextResponse.next(). In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.
All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.
More details at Vercel Changelog