Moment.js saw a minor version bump from 2.26.0 to 2.27.0, with the latter released on June 18, 2020, compared to the former's release date of May 20, 2020. Both versions serve the same core purpose: parsing, validating, manipulating, and displaying dates in JavaScript. Examining the devDependencies section, there are no immediately evident differences between the two, suggesting similar tooling and testing approaches were employed. The core development dependencies for testing and building remained consistent between versions, including tools like nyc, grunt, karma, eslint, rollup, prettier, and several Grunt-related utilities. The lack of changes in dependencies indicates that the new version focused mainly on bug fixes, performance improvements, or minor feature enhancements rather than adopting new development paradigms or frameworks.
The dist section shows subtle differences. Version 2.27.0 has a fileCount of 527 and an unpackedSize of 4,118,073 bytes, while version 2.26.0 has a fileCount of 524 and an unpackedSize of 4,091,021 bytes. The increased file count and unpacked size suggests that the newer version includes small additions or adjustments. This information is pertinent for developers concerned about bundle sizes or potential performance implications when including the library in their projects. While both versions share the same licensing (MIT) and repository details, the newer version likely contains incremental updates that improve overall stability and correctness based on user feedback and ongoing maintenance.
All the vulnerabilities related to the version 2.27.0 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.
