The next package, a Node.js extension library, saw a minor version update from 0.2.8 to 0.2.9, introducing subtle but potentially important refinements. Both versions share identical dependencies, relying on es5-ext (version 0.7.x) and deferred (version 0.4.x) for extended ECMAScript 5 functionalities and deferred/promise management respectively, and tad (version 0.1.x) as a dev dependency. The core functionality, built around extending Node.js capabilities remains consistent.
The key difference lies in the release date, with version 0.2.9 arriving on January 26, 2012, roughly four days after version 0.2.8's release on January 22, 2012. While the specifics of the changes aren't explicitly detailed in the provided metadata, the quick succession suggests bug fixes, performance improvements, or very minor feature additions made in the newer version.
For developers considering using or updating the next package, this information suggests a stable and actively maintained library (at least at the time of release). Utilizing version 0.2.9 would likely provide a more polished experience due to the implied refinements. The package's reliance on es5-ext indicates a focus on extending JavaScript capabilities, while the deferred dependency points to asynchronous programming support. The package, authored by Mariusz Nowak and hosted on GitHub, has Node.js extensions to offer.
All the vulnerabilities related to the version 0.2.9 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