-
Notifications
You must be signed in to change notification settings - Fork 32
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
chore(deps): update dependency qs [security] - autoclosed #1678
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-qs-vulnerability
branch
from
December 13, 2022 11:52
09e1b6c
to
c006897
Compare
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
2 times, most recently
from
December 28, 2022 10:59
05f293c
to
352bee7
Compare
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
5 times, most recently
from
January 19, 2023 05:16
f688c3a
to
cfb9fa5
Compare
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
8 times, most recently
from
February 4, 2023 15:07
b544518
to
4a3eeb4
Compare
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
2 times, most recently
from
February 15, 2023 16:29
f640961
to
8ca5078
Compare
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
3 times, most recently
from
February 28, 2023 00:29
ad2abcc
to
4a88392
Compare
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
5 times, most recently
from
March 20, 2023 12:08
4cb4ae0
to
142cd18
Compare
renovate
bot
changed the title
chore(deps): update dependency qs [security]
chore(deps): update dependency qs [security] - autoclosed
Mar 24, 2023
renovate
bot
changed the title
chore(deps): update dependency qs [security] - autoclosed
chore(deps): update dependency qs [security]
Mar 25, 2023
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
from
April 10, 2023 20:29
d1bf4bc
to
034452d
Compare
renovate
bot
changed the title
chore(deps): update dependency qs [security]
chore(deps): update dependency qs to 6.5.3 [security]
Apr 11, 2023
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
from
April 11, 2023 21:54
034452d
to
a7736ca
Compare
renovate
bot
changed the title
chore(deps): update dependency qs to 6.5.3 [security]
chore(deps): update dependency qs to 6.5.3 [security] - autoclosed
Apr 17, 2023
renovate
bot
changed the title
chore(deps): update dependency qs to 6.5.3 [security] - autoclosed
chore(deps): update dependency qs to 6.5.3 [security]
Apr 18, 2023
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
from
April 18, 2023 23:32
a7736ca
to
6baa448
Compare
renovate
bot
changed the title
chore(deps): update dependency qs to 6.5.3 [security]
chore(deps): update dependency qs to 6.5.3 [security] - autoclosed
Apr 25, 2023
renovate
bot
changed the title
chore(deps): update dependency qs to 6.5.3 [security] - autoclosed
chore(deps): update dependency qs to 6.5.3 [security]
Apr 26, 2023
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
2 times, most recently
from
May 2, 2023 12:23
072e52d
to
f6c6660
Compare
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
from
May 3, 2023 21:42
f6c6660
to
00dfeef
Compare
renovate
bot
changed the title
chore(deps): update dependency qs to 6.5.3 [security]
chore(deps): update dependency qs [security]
May 3, 2023
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
from
May 8, 2023 13:29
00dfeef
to
3170018
Compare
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
4 times, most recently
from
May 22, 2023 11:38
57cf911
to
65f560d
Compare
renovate
bot
force-pushed
the
renovate/npm-qs-vulnerability
branch
from
May 26, 2023 05:34
65f560d
to
82cbdbb
Compare
renovate
bot
changed the title
chore(deps): update dependency qs [security]
chore(deps): update dependency qs [security] - autoclosed
May 28, 2023
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:
6.5.2
->6.5.3
6.7.0
->6.7.3
6.10.1
->6.10.3
6.9.3
->6.9.7
GitHub Vulnerability Alerts
CVE-2022-24999
qs before 6.10.3 allows attackers to cause a Node process hang because an
__ proto__
key can be used. In many typical web framework use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such asa[__proto__]=b&a[__proto__]&a[length]=100000000
. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4.Configuration
📅 Schedule: Branch creation - "" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.