Moment.js saw a minor version bump from 2.19.2 to 2.19.3, primarily distinguished by its release date. Version 2.19.3 arrived on November 29, 2017, roughly two weeks after version 2.19.2, which was released on November 11, 2017. While both versions share the identical core set of development dependencies, covering tools like nyc for code coverage, grunt for task automation, karma for testing, and rollup for module bundling, the update suggests incremental improvements or bug fixes rather than a significant overhaul of features.
For developers using Moment.js, this means the core functionality for parsing, validating, manipulating, and displaying dates remains consistent. The uniform devDependencies indicates a continued commitment to testing, code quality (via grunt-jscs and grunt-contrib-jshint), and build processes. Users can likely upgrade from 2.19.2 to 2.19.3 with minimal concern for breaking changes, benefiting from any refinements or patches included in the newer release. Both versions are licensed under MIT and maintained within the same GitHub repository, ensuring the library's accessibility and collaborative development. The author information also remains consistent – attributed to Iskren Ivov Chernev.
All the vulnerabilities related to the version 2.19.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.
