Next.js version 0.2.0 represents an incremental update over its predecessor, version 0.1.1, bringing enhanced functionality to this Node.js extensions library. Both versions, authored by Mariusz Nowak and released under the same repository, aim to provide helpful extensions tailored to Node.js development. The key difference lies in the introduced dependency on the "deferred" package (version 0.2.x), alongside an update to the "es5-ext" dependency, moving from version 0.5.x to 0.6.x.
For developers, specifically those reliant on asynchronous programming patterns, the introduction of the "deferred" package in v0.2.0 offers a significant advantage. By including "deferred," the package likely enhances its capabilities for managing asynchronous operations, promises, or related asynchronous constructs within Node.js applications. Consider this if your code base needs advanced control on asynchronous execution.
While both versions depend on "es5-ext" to provide enhancements to ECMAScript 5 functionalities, the update from version 0.5.x to 0.6.x suggests improvements, bug fixes, or expanded functionalities within the core ECMAScript 5 extensions. Developers should review the change log for "es5-ext" during this upgrade period to understand the specific benefits. If you want the newest features in ECMAScript 5, you might want to update.
All the vulnerabilities related to the version 0.2.0 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