Next.js, a Node.js extension library, saw a minor version update from 0.2.2 to 0.2.3 in August 2011. While the core dependencies on "es5-ext" (version 0.6.x) and "deferred" (version 0.2.x) remained consistent, indicating no breaking API changes or fundamental architectural shifts, developers should note the slight change in release date, with version 0.2.3 being published on August 12, 2011, a day after version 0.2.2. This suggests that version 0.2.3 likely contains bug fixes, performance improvements, or small feature enhancements that merited a quick update.
The development dependencies, including "tad" (version 0.1.x), stayed the same, implying no alterations to the testing or build processes. Both versions point to the same repository on GitHub, managed by Mariusz Nowak, suggesting the library's evolution remains under the same author and codebase. For developers relying on Next.js, upgrading to version 0.2.3 is recommended to benefit from any potential bug fixes and improvements, especially given the minimal nature of the version bump. The library offers useful extensions and utilities for Node.js development, facilitating enhanced Javascript capabilities and asynchronous task management with the help of the deferred dependency. Check the project's commit history on GitHub for detailed information on the exact changes introduced in version 0.2.3 or explore newer versions of the package.
All the vulnerabilities related to the version 0.2.3 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