Next version 0.2.2 is a minor update to the Node.js extensions library, building upon the foundation laid by version 0.2.1. Both versions, authored by Mariusz Nowak and maintained at Medikoo, provide utilities that enhance Node.js development. Core dependencies like es5-ext and deferred remain consistent across both releases, ensuring compatibility and continued support for ECMAScript 5 extensions and deferred/promise patterns. Similarly, the tad testing framework is listed as a dev dependency in both.
The key change lies in the release date; version 0.2.2 was released on August 11, 2011, a mere three days after version 0.2.1 (August 8, 2011). This suggests that version 0.2.2 likely addresses bug fixes, minor enhancements, or perhaps crucial updates discovered shortly after the 0.2.1 release. While the specific changes aren't detailed in this metadata, developers considering using or upgrading to version 0.2.2 should investigate release notes or commit history for precise details on the improvements.
For developers using or considering next, the enduring dependencies indicate a commitment to established technologies for asynchronous operations and language feature support. The small jump in version number highlights the importance of staying up-to-date with even seemingly minor releases to benefit from potentially critical fixes and optimizations. The library supports efficient, modern and readable code.
All the vulnerabilities related to the version 0.2.2 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