Skip to content
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

[Snyk] Fix for 1 vulnerabilities #84

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

adamlaska
Copy link
Owner

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:
    • docs/package.json
    • docs/package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 658/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
No Proof of Concept

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

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:

🦉 Regular Expression Denial of Service (ReDoS)

@google-cla
Copy link

google-cla bot commented Jun 20, 2023

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@socket-security
Copy link

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

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

Issue Package Version Note Source
Network access domutils 2.8.0 docs/package-lock.json via @docusaurus/core@2.0.0, @docusaurus/preset-classic@2.0.0, @docusaurus/theme-search-algolia@2.0.0
Network access domutils 3.1.0 docs/package-lock.json via @docusaurus/preset-classic@2.0.0, @docusaurus/theme-search-algolia@2.0.0
Network access svgo 2.8.0 docs/package-lock.json via @docusaurus/core@2.0.0, @docusaurus/preset-classic@2.0.0, @docusaurus/theme-search-algolia@2.0.0
Network access webpack-dev-server 4.15.1 docs/package-lock.json via @docusaurus/core@2.0.0, @docusaurus/preset-classic@2.0.0, @docusaurus/theme-search-algolia@2.0.0
Network access search-insights 2.6.0 docs/package-lock.json via @docusaurus/preset-classic@2.0.0, @docusaurus/theme-search-algolia@2.0.0
Network access express 4.18.2 docs/package-lock.json via @docusaurus/core@2.0.0, @docusaurus/preset-classic@2.0.0, @docusaurus/theme-search-algolia@2.0.0
Network access bonjour-service 1.1.1 docs/package-lock.json via @docusaurus/core@2.0.0, @docusaurus/preset-classic@2.0.0, @docusaurus/theme-search-algolia@2.0.0
Network access http-proxy-middleware 2.0.6 docs/package-lock.json via @docusaurus/core@2.0.0, @docusaurus/preset-classic@2.0.0, @docusaurus/theme-search-algolia@2.0.0

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore domutils@2.8.0
  • @SocketSecurity ignore domutils@3.1.0
  • @SocketSecurity ignore svgo@2.8.0
  • @SocketSecurity ignore webpack-dev-server@4.15.1
  • @SocketSecurity ignore search-insights@2.6.0
  • @SocketSecurity ignore express@4.18.2
  • @SocketSecurity ignore bonjour-service@1.1.1
  • @SocketSecurity ignore http-proxy-middleware@2.0.6

@socket-security
Copy link

New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives1 Size Publisher
@docusaurus/core ⬆️ 2.0.0-beta.0...2.0.0 eval +258/-205 76.3 MB slorber
@docusaurus/preset-classic ⬆️ 2.0.0-beta.0...2.0.0 None +325/-258 89.9 MB slorber
clsx ⬆️ 1.1.1...1.2.1 None +0/-0 5.67 kB lukeed
postcss ⬆️ 8.2.15...8.4.24 None +2/-1 363 kB ai
@docusaurus/theme-search-algolia ⬆️ 2.0.0-beta.0...2.0.0 None +305/-236 83.5 MB slorber

Footnotes

  1. https://docs.socket.dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants