[Snyk] Security upgrade geckodriver from 2.0.4 to 4.0.0

[alejandrosuarez]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json
  • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	718/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 6.5	Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-JS-TAR-6476909	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: geckodriver

The new version differs by 27 commits.

• 938b8ea Merge pull request Bigger sota patch 4 qeeqbox/social-analyzer#115 from webdriverio-community/cb-project-rewrite
• e806d1e fix macos downloads
• 5943168 update changelog
• f965bb8 update gitignore
• c20a8a7 remove binary from development
• c619772 debug
• ef89b6a fix deps
• b3ba66b support setting custom CDN url
• 04a92cd rewrite project to use latest dev standards
• 64aaced Bump minimatch from 3.0.4 to 3.1.2 (The problem with getting the result #Question qeeqbox/social-analyzer#111)
• 24ebe27 Bump http-cache-semantics from 4.1.0 to 4.1.1 (deleted qeeqbox/social-analyzer#110)
• d7a01a7 Drop support for node 12 (NodeWebapp Windows qeeqbox/social-analyzer#109)
• d72433a 3.2.0
• ec29033 Add ARM64 support (Create geckodriver-path.cjs qeeqbox/social-analyzer#108)
• ec8fdd5 Update README.md
• c65b4af 3.1.0
• c963479 Update geckodriver and some deps (Added npm update to the README.md qeeqbox/social-analyzer#106)
• b27ed5d 3.0.3 – update geckodriver (Linux Node WebApp installation is failing qeeqbox/social-analyzer#105)
• 2193d0c 3.0.2
• a739465 Bump trim-off-newlines from 1.0.1 to 1.0.3 (Update package-lock.json qeeqbox/social-analyzer#102)
• 577d9dc Bump ansi-regex from 4.1.0 to 4.1.1 (Bump http-cache-semantics from 4.1.0 to 4.1.1 qeeqbox/social-analyzer#103)
• 06ccac4 Bump got from 11.8.2 to 11.8.5 ([deleted] qeeqbox/social-analyzer#101)
• 1aaf7f3 Bump minimist from 1.2.5 to 1.2.6 (How does one start the web app?  qeeqbox/social-analyzer#100)
• 9aa99d7 3.0.1

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled Resource Consumption ('Resource Exhaustion')

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, network Transitive: eval, filesystem	+66	12.1 MB	wdio-user

🚮 Removed packages: npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/[email protected]	Install script: postinstall Source: test -f ./dist/install.js && node ./dist/install.js || echo "Skipping install, project not build!"	package-lock.json package.json

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]