-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency moment to v2.29.4 [security] - autoclosed #252
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
April 29, 2022 13:38
50d2744
to
dac5320
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
3 times, most recently
from
June 23, 2022 12:06
8595024
to
6a8e5fc
Compare
renovate
bot
changed the title
chore(deps): update dependency moment to 2.29.2 [security]
chore(deps): update dependency moment to 2.29.2 [SECURITY]
Jun 27, 2022
renovate
bot
changed the title
chore(deps): update dependency moment to 2.29.2 [SECURITY]
chore(deps): update dependency moment to 2.29.2 [security]
Jun 28, 2022
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
June 29, 2022 07:32
6a8e5fc
to
d6f01f8
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
July 8, 2022 11:36
d6f01f8
to
e90c4ec
Compare
renovate
bot
changed the title
chore(deps): update dependency moment to 2.29.2 [security]
chore(deps): update dependency moment to 2.29.4 [security]
Jul 8, 2022
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
July 19, 2022 07:08
e90c4ec
to
ae9a101
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
2 times, most recently
from
July 27, 2022 12:17
356208d
to
89e2b47
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
August 4, 2022 08:41
89e2b47
to
3076bfe
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #252 +/- ##
=======================================
Coverage 84.71% 84.71%
=======================================
Files 174 174
Lines 3645 3645
Branches 880 872 -8
=======================================
Hits 3088 3088
Misses 543 543
Partials 14 14 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
2 times, most recently
from
September 13, 2022 13:09
8d5e24f
to
8277557
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
October 6, 2022 17:40
8277557
to
6d714d7
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
3 times, most recently
from
October 25, 2022 14:52
620b52f
to
3efbf7a
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
2 times, most recently
from
December 7, 2022 10:14
28d7450
to
cd6e108
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
December 15, 2022 06:52
cd6e108
to
59ff8b1
Compare
renovate
bot
changed the title
chore(deps): update dependency moment to 2.29.4 [security]
Update dependency moment to 2.29.4 [SECURITY]
Dec 17, 2022
renovate
bot
changed the title
Update dependency moment to 2.29.4 [SECURITY]
chore(deps): update dependency moment to 2.29.4 [security]
Dec 17, 2022
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
3 times, most recently
from
January 2, 2023 15:14
4f84e71
to
819b673
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
2 times, most recently
from
January 11, 2023 06:28
625b8ea
to
2e7e4ca
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
October 20, 2023 21:25
6b564fb
to
470caee
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
2 times, most recently
from
November 1, 2023 05:43
be088fb
to
e5901aa
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
2 times, most recently
from
December 1, 2023 16:08
25d28a8
to
ac6237f
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
4 times, most recently
from
December 11, 2023 17:59
94e9921
to
65bcd83
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
December 12, 2023 23:20
65bcd83
to
c7a8ae6
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
January 18, 2024 14:52
c7a8ae6
to
abb7962
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
February 8, 2024 19:30
abb7962
to
0ee834b
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
2 times, most recently
from
March 20, 2024 13:32
95c4ac5
to
b0594ce
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
2 times, most recently
from
March 29, 2024 14:52
c6b6dc7
to
b142de1
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
April 16, 2024 02:46
b142de1
to
7d10dea
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
June 17, 2024 15:01
7d10dea
to
d35f56f
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
July 1, 2024 15:05
d35f56f
to
69f9235
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
July 25, 2024 16:46
69f9235
to
be484f9
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
2 times, most recently
from
August 6, 2024 17:30
438a2a3
to
9f21c08
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
August 9, 2024 15:31
9f21c08
to
5b2cc20
Compare
renovate
bot
force-pushed
the
renovate/npm-moment-vulnerability
branch
from
August 15, 2024 13:16
5b2cc20
to
da5e1d4
Compare
renovate
bot
changed the title
fix(deps): update dependency moment to v2.29.4 [security]
fix(deps): update dependency moment to v2.29.4 [security] - autoclosed
Aug 15, 2024
auto-merge was automatically disabled
August 15, 2024 13:29
Pull request was closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.29.1
->2.29.4
GitHub Vulnerability Alerts
CVE-2022-24785
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:
CVE-2022-31129
Impact
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.Release Notes
moment/moment (moment)
v2.29.4
Compare Source
v2.29.3
Compare Source
v2.29.2
Compare Source
Address GHSA-8hfj-j24r-96c4
Configuration
📅 Schedule: Branch creation - "" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.