Next version 0.2.10 and its predecessor, 0.2.9, are minor releases of a Node.js extension library aimed at streamlining development workflows. Both versions share fundamental characteristics, offering crucial dependencies like es5-ext (version 0.7.x) for enhanced ECMAScript 5 functionalities and deferred (version 0.4.x) for managing asynchronous operations efficiently. Development tools, particularly tad (version 0.1.x) remain consistent across both versions, ensuring a stable testing environment. The core purpose of the library, providing Node.js extensions, remains unchanged, indicating an emphasis on incremental improvements and bug fixes rather than radical feature additions.
The key difference between the two versions lies within their release dates. Version 0.2.10 was published on January 26, 2012, at 20:31:31.609Z, while version 0.2.9 was released earlier on the same day at 15:05:12.204Z. This suggests that version 0.2.10 likely incorporates minor bug fixes, optimizations, or documentation adjustments identified shortly after the release of version 0.2.9. While the changes might be subtle, developers are encouraged to upgrade to the latest version (0.2.10) to benefit from any potential improvements, ensuring they are working with the most refined iteration of the next library. Both versions are accessible through the npm registry, utilizing the same repository and authored by Mariusz Nowak.
All the vulnerabilities related to the version 0.2.10 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