webdriverio: [🐛 Bug]: WebdriverIO security vulnerability in dependency on puppeteer-core
Have you read the Contributing Guidelines on issues?
- I have read the Contributing Guidelines on issues.
WebdriverIO Version
8.39.0
Node.js Version
18.18.2
Mode
Standalone Mode
Which capabilities are you using?
No response
What happened?
Webdriverio needs to update its dependency version of puppeteer-core to at least 22.11.2 - puppeteer is depending on a vulnerable version of WS that they fixed in their 22.11.2 release.
What is your expected behavior?
No response
How to reproduce the bug.
get latest webdriverio and run npm audit
Relevant log output
npm audit output:
ws 8.0.0 - 8.17.0
Severity: high
ws affected by a DoS when handling a request with many HTTP headers - https://github.com/advisories/GHSA-3h5v-q93c-6h6q
fix available via `npm audit fix --force`
Will install @wdio/browserstack-service@7.16.4, which is a breaking change
node_modules/puppeteer-core/node_modules/ws
node_modules/ws
puppeteer-core 11.0.0 - 22.11.1
Depends on vulnerable versions of ws
node_modules/puppeteer-core
webdriverio 7.16.5 - 8.39.0
Depends on vulnerable versions of puppeteer-core
node_modules/@wdio/browserstack-service/node_modules/webdriverio
node_modules/webdriverio
<snip>
Code of Conduct
- I agree to follow this project’s Code of Conduct
Is there an existing issue for this?
- I have searched the existing issues
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19 (9 by maintainers)
For those who cannot wait you can suppress the audit error by adding the following block to your
package.jsonWithin the next 1-2 month.
Can we please calm down? I’m not trying to be nasty about this. When do you expect v9 to release?
Hmm. I only ask because I’m not sure how long I have before somebody starts breathing down my neck about why we are using packages that have unfixed “critical vulnerabilities,” even if by my understanding those vulnerabilities won’t actually affect us in practice. A lot of people see the npm audit message “8 critical vulnerabilities” and go into panic mode. As the point person for Selenium/Webdriverio stuff at my company, I’ve already gotten several concerned emails from various internal parties.