Moment.js version 2.19.0, released on October 10, 2017, brings the familiar date parsing, validation, and manipulation capabilities developers rely on, building upon the foundation of version 2.18.1 released earlier on March 21, 2017. Both versions share the same core functionality and developer dependencies, including tools for testing (karma, qunit), bundling (rollup), code quality (grunt-jscs, grunt-jshint), and build automation (grunt). Developers familiar with the 2.18.1 release will find a similar development environment in 2.19.0, enabling a smooth transition.
While the core features remain consistent, the update signifies ongoing maintenance and potential bug fixes or minor enhancements incorporated into the library. Users should note the updated release date suggesting improvements and refinements made during the intervening months. For projects already using Moment.js, upgrading ensures access to the latest improvements and a more stable experience. As with all dependency updates, developers should review release notes and test their applications thoroughly to confirm compatibility and identify any edge cases. Version 2.19.0 continues to empower developers to easily interact with dates and times, making it a reliable companion for JavaScript projects requiring date management.
All the vulnerabilities related to the version 2.19.0 of the package
Regular Expression Denial of Service in moment
Affected versions of moment are vulnerable to a low severity regular expression denial of service when parsing dates as strings.
Update to version 2.19.3 or later.
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.
