Skip to content

Update dependency moment to v2.29.4 [SECURITY]#108

Open
renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/npm-moment-vulnerability
Open

Update dependency moment to v2.29.4 [SECURITY]#108
renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/npm-moment-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Apr 15, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
moment (source) 2.24.02.29.4 age confidence

Path Traversal: 'dir/../../filename' in moment.locale

CVE-2022-24785 / GHSA-8hfj-j24r-96c4

More information

Details

Impact

This vulnerability impacts npm (server) users of moment.js, especially if user provided locale string, eg fr is directly used to switch moment locale.

Patches

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).

Workarounds

Sanitize user-provided locale name before passing it to moment.js.

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Moment.js vulnerable to Inefficient Regular Expression Complexity

CVE-2022-31129 / GHSA-wc69-rhjr-hc9g

More information

Details

Impact
  • using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs
  • noticeable slowdown is observed with inputs above 10k characters
  • users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks
Patches

The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking.

Workarounds

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.

References

There is an excellent writeup of the issue here: https://github.com/moment/moment/pull/6015#issuecomment-1152961973=

Details

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.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

moment/moment (moment)

v2.29.4

Compare Source

  • Release Jul 6, 2022
    • #​6015 [bugfix] Fix ReDoS in preprocessRFC2822 regex

v2.29.3

Compare Source

  • Release Apr 17, 2022

v2.29.2

Compare Source

  • Release Apr 3 2022

Address GHSA-8hfj-j24r-96c4

v2.29.1

Compare Source

  • Release Oct 6, 2020

Updated deprecation message, bugfix in hi locale

v2.29.0

Compare Source

  • Release Sept 22, 2020

New locales (es-mx, bn-bd).
Minor bugfixes and locale improvements.
More tests.
Moment is in maintenance mode. Read more at this link:
https://momentjs.com/docs/#/-project-status/

v2.28.0

Compare Source

  • Release Sept 13, 2020

Fix bug where .format() modifies original instance, and locale updates

v2.27.0

Compare Source

  • Release June 18, 2020

Added Turkmen locale, other locale improvements, slight TypeScript fixes

v2.26.0

Compare Source

  • Release May 19, 2020

TypeScript fixes and many locale improvements

v2.25.3

Compare Source

  • Release May 4, 2020

Remove package.json module property. It looks like webpack behaves differently
for modules loaded via module vs jsnext:main.

v2.25.2

Compare Source

  • Release May 4, 2020

This release includes ES Module bundled moment, separate from it's source code
under dist/ folder. This might alleviate issues with finding the `./locale
subfolder for loading locales. This might also mean now webpack will bundle all
locales automatically, unless told otherwise.

v2.25.1

Compare Source

  • Release May 1, 2020

This is a quick patch release to address some of the issues raised after
releasing 2.25.0.

  • 2e268635 [misc] Revert #​5269 due to webpack warning
  • 226799e1 [locale] fil: Fix metadata comment
  • a83a521 [bugfix] Fix typeoff usages
  • e324334 [pkg] Add ts3.1-typings in npm package
  • 28cc23e [misc] Remove deleted generated locale en-SG

v2.25.0

Compare Source

  • Release May 1, 2020

  • #​4611 022dc038 [feature] Support for strict string parsing, fixes #​2469

  • #​4599 4b615b9d [feature] Add support for eras in en and jp

  • #​4296 757d4ff8 [feature] Accept custom relative thresholds in duration.humanize

  • 18 bigfixes

  • 36 locale fixes

  • 5 new locales (oc-lnc, zh-mo, en-in, gom-deva, fil)


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Apr 15, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: eslint-plugin-graphql@2.1.1
npm warn Found: graphql@14.2.0
npm warn node_modules/graphql
npm warn   peer graphql@"^14.1.0" from @gatsbyjs/relay-compiler@2.0.0-printer-fix.2
npm warn   node_modules/@gatsbyjs/relay-compiler
npm warn     @gatsbyjs/relay-compiler@"2.0.0-printer-fix.2" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm warn   9 more (apollo-link, apollo-utilities, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer graphql@"^0.12.0 || ^0.13.0" from eslint-plugin-graphql@2.1.1
npm warn node_modules/eslint-plugin-graphql
npm warn   eslint-plugin-graphql@"^2.0.0" from gatsby@2.3.4
npm warn   node_modules/gatsby
npm warn
npm warn Conflicting peer dependency: graphql@0.13.2
npm warn node_modules/graphql
npm warn   peer graphql@"^0.12.0 || ^0.13.0" from eslint-plugin-graphql@2.1.1
npm warn   node_modules/eslint-plugin-graphql
npm warn     eslint-plugin-graphql@"^2.0.0" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: express-graphql@0.6.12
npm warn Found: graphql@14.2.0
npm warn node_modules/graphql
npm warn   peer graphql@"^14.1.0" from @gatsbyjs/relay-compiler@2.0.0-printer-fix.2
npm warn   node_modules/@gatsbyjs/relay-compiler
npm warn     @gatsbyjs/relay-compiler@"2.0.0-printer-fix.2" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm warn   9 more (apollo-link, apollo-utilities, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer graphql@"^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0" from express-graphql@0.6.12
npm warn node_modules/express-graphql
npm warn   express-graphql@"^0.6.12" from gatsby@2.3.4
npm warn   node_modules/gatsby
npm warn
npm warn Conflicting peer dependency: graphql@0.13.2
npm warn node_modules/graphql
npm warn   peer graphql@"^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0" from express-graphql@0.6.12
npm warn   node_modules/express-graphql
npm warn     express-graphql@"^0.6.12" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: gatsby-plugin-sass@2.0.11
npm error Found: node-sass@7.0.0
npm error node_modules/node-sass
npm error   node-sass@"7.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer node-sass@"^4.9.0" from gatsby-plugin-sass@2.0.11
npm error node_modules/gatsby-plugin-sass
npm error   gatsby-plugin-sass@"2.0.11" from the root project
npm error
npm error Conflicting peer dependency: node-sass@4.14.1
npm error node_modules/node-sass
npm error   peer node-sass@"^4.9.0" from gatsby-plugin-sass@2.0.11
npm error   node_modules/gatsby-plugin-sass
npm error     gatsby-plugin-sass@"2.0.11" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-06-13T16_08_35_396Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-13T16_08_35_396Z-debug-0.log

@renovate renovate Bot changed the title Update dependency moment to v2.29.4 [SECURITY] Update dependency moment to v2.29.4 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot deleted the renovate/npm-moment-vulnerability branch April 27, 2026 18:46
@renovate renovate Bot changed the title Update dependency moment to v2.29.4 [SECURITY] - autoclosed Update dependency moment to v2.29.4 [SECURITY] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate renovate Bot force-pushed the renovate/npm-moment-vulnerability branch 2 times, most recently from c16c2af to 913706e Compare April 27, 2026 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants