Moment.js version 2.25.3 is a minor release update to the popular JavaScript date manipulation library, following closely after version 2.25.2. Both maintain the core functionality of parsing, validating, manipulating, and displaying dates and times in JavaScript. As minor releases, the key difference between these versions likely lies in bug fixes, performance improvements, or potentially, very minor feature enhancements that don't break existing APIs.
Developers considering an upgrade from 2.25.2 to 2.25.3 should focus on the benefits of incorporating the newest bug fixes. The unpackedSize increases slightly from 4056041 to 4056168, indicating internal changes, potentially adjustments to locales data or new features which may improve the developer experience.
The developer dependencies remain identical between the two releases; including tools like nyc for coverage, eslint for linting, rollup for bundling, prettier for code formatting, and various Grunt tasks for automation, signaling a consistent development and testing environment. The shared MIT license provides developers with significant freedom in how they use and distribute the library. Given the rapid release cycle—roughly 3 hours between the two versions—it is safe to say that the maintainers aim to provide continuous value and quality.
All the vulnerabilities related to the version 2.25.3 of the package
Path Traversal: 'dir/../../filename' in moment.locale
This vulnerability impacts npm (server) users of moment.js, especially if user provided locale string, eg fr is directly used to switch moment locale.
This problem is patched in 2.29.2, and the patch can be applied to all affected versions (from 1.0.1 up until 2.29.1, inclusive).
Sanitize user-provided locale name before passing it to moment.js.
Are there any links users can visit to find out more?
If you have any questions or comments about this advisory:
Moment.js vulnerable to Inefficient Regular Expression Complexity
The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking.
In general, given the proliferation of ReDoS attacks, it makes sense to limit the length of the user input to something sane, like 200 characters or less. I haven't seen legitimate cases of date-time strings longer than that, so all moment users who do pass a user-originating string to constructor are encouraged to apply such a rudimentary filter, that would help with this but also most future ReDoS vulnerabilities.
There is an excellent writeup of the issue here: https://github.com/moment/moment/pull/6015#issuecomment-1152961973=
The issue is rooted in the code that removes legacy comments (stuff inside parenthesis) from strings during rfc2822 parsing. moment("(".repeat(500000)) will take a few minutes to process, which is unacceptable.
