Moment.js version 2.22.1 represents a minor update over the prior stable release, version 2.22.0, of this widely used JavaScript date and time manipulation library. Both versions share the same core functionality offering developers robust tools for parsing, validating, manipulating, and displaying dates in JavaScript environments. The development dependencies remain largely consistent, indicating stability in the tooling used to build and test the library, although a notable change shows the upgrade of the qunit version from 0.7.5 to ^2.6.0 which suggests improvements or fixes in testing approaches. This might indicate more modern testing implementations ensuring greater reliability.
From a developer’s perspective, the key difference lies in the release date and possibly some subtle bug fixes or performance improvements incorporated in 2.22.1, which are not explicitly detailed. The file count remains the same for both versions, but there's a minor difference in unpackedSize, hinting at possible refactoring or minor additions. Users should consider upgrading to version 2.22.1 to benefit from any fixes and potential performance enhancements made since 2.22.0 to assure the best and most stable experience using moment.js. Both versions are under the MIT license and are available on GitHub, thus maintaining this library developer-friendly nature.
All the vulnerabilities related to the version 2.22.1 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.
