-
Notifications
You must be signed in to change notification settings - Fork 22
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 chromedriver to v119 [security] #611
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-chromedriver-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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-chromedriver-vulnerability
branch
from
November 29, 2023 08:15
039c295
to
0eb24e4
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
2 times, most recently
from
November 30, 2023 12:18
ddebd87
to
3c9b025
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
from
December 27, 2023 04:41
3c9b025
to
d33a501
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
15 times, most recently
from
January 2, 2024 00:50
d21861e
to
7d09c99
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
from
January 8, 2024 21:59
7d09c99
to
976624e
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
from
April 5, 2024 21:58
7a19278
to
e9589ed
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
3 times, most recently
from
May 2, 2024 13:25
cf6b77b
to
74d16c2
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
from
May 3, 2024 07:12
74d16c2
to
3f41941
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
4 times, most recently
from
May 10, 2024 03:49
f38c80c
to
14907ba
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
from
May 13, 2024 18:54
14907ba
to
e9c2247
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
from
May 21, 2024 17:26
e9c2247
to
fb00bfb
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
9 times, most recently
from
May 29, 2024 13:52
fb9c38a
to
26cf758
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
4 times, most recently
from
June 5, 2024 19:51
41b812e
to
c6cbb5f
Compare
renovate
bot
force-pushed
the
renovate/npm-chromedriver-vulnerability
branch
from
June 5, 2024 23:06
c6cbb5f
to
72773a6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
115.0.1
->119.0.1
GitHub Vulnerability Alerts
CVE-2023-26156
Versions of the package chromedriver before 119.0.1 are vulnerable to Command Injection when setting the chromedriver.path to an arbitrary system binary. This could lead to unauthorized access and potentially malicious actions on the host system.
Note:
An attacker must have access to the system running the vulnerable chromedriver library to exploit it. The success of exploitation also depends on the permissions and privileges of the process running chromedriver.
Release Notes
giggio/node-chromedriver (chromedriver)
v119.0.1
Compare Source
v119.0.0
Compare Source
v118.0.1
Compare Source
v118.0.0
Compare Source
v117.0.3
Compare Source
v117.0.2
Compare Source
v117.0.1
Compare Source
v117.0.0
Compare Source
v116.0.0
Compare Source
Configuration
📅 Schedule: Branch creation - "" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.