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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Fix for 2 vulnerabilities #68

Closed
wants to merge 1 commit into from
Closed

[Snyk] Fix for 2 vulnerabilities #68

wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Feb 4, 2023

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
high severity 798/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 8.1		 Remote Code Execution (RCE)
SNYK-JS-ETA-2936803		 No Proof of Concept
medium severity 556/1000
Why? Recently disclosed, Has a fix available, CVSS 5.4		 Cross-site Scripting (XSS)
SNYK-JS-ETA-3261240		 No No Known Exploit

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

Commit messages
Package name: @docusaurus/preset-classic The new version differs by 250 commits.

See the full diff

Package name: @docusaurus/theme-search-algolia The new version differs by 250 commits.

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:

🦉 Remote Code Execution (RCE)
🦉 Cross-site Scripting (XSS)

@socket-security
Copy link

Socket Security Pull Request Report

Dependency issues detected. If you merge this pull request, you will not be alerted to the instances of these issues again.

📜 Install scripts

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.

Package Script field Source
core-js@3.27.2 (upgraded) postinstall docs/package-lock.json via @docusaurus/core@2.0.0-beta.0, @docusaurus/preset-classic@2.3.1, @docusaurus/theme-search-algolia@2.3.1
core-js@3.9.0 (upgraded) postinstall explorer/package-lock.json via react-scripts@4.0.3
core-js-pure@3.27.2 (upgraded) postinstall docs/package-lock.json via @docusaurus/core@2.0.0-beta.0, @docusaurus/preset-classic@2.3.1, @docusaurus/theme-search-algolia@2.3.1
core-js-pure@3.6.5 (upgraded) postinstall explorer/package-lock.json via react-scripts@4.0.3
😵‍💫 Bin script confusion

This package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack

Consider removing one of the conflicting packages. Packages should only export bin scripts with their name

Package Bin script Source
ansi-html@0.0.7 (added) ansi-html docs/package-lock.json via @docusaurus/core@2.0.0-beta.0, explorer/package-lock.json via react-scripts@4.0.3
ansi-html-community@0.0.8 (added) ansi-html docs/package-lock.json via @docusaurus/preset-classic@2.3.1, @docusaurus/theme-search-algolia@2.3.1
Pull request report summary
Issue Status
Install scripts ⚠️ 4 issues
Native code ✅ 0 issues
Bin script confusion ⚠️ 2 issues
Bin script shell injection ✅ 0 issues
Unresolved require ✅ 0 issues
Invalid package.json ✅ 0 issues
HTTP dependency ✅ 0 issues
Git dependency ✅ 0 issues
Potential typo squat ✅ 0 issues
Known Malware ✅ 0 issues
Telemetry ✅ 0 issues
Protestware/Troll package ✅ 0 issues
Bot Commands

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@2.4.2

  • @SocketSecurity ignore core-js@3.27.2
  • @SocketSecurity ignore core-js@3.9.0
  • @SocketSecurity ignore core-js-pure@3.27.2
  • @SocketSecurity ignore core-js-pure@3.6.5
  • @SocketSecurity ignore ansi-html@0.0.7

Powered by socket.dev

@stale
Copy link

stale bot commented May 21, 2023

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label May 21, 2023
@stale
Copy link

stale bot commented Jun 18, 2023

This stale pull request has been automatically closed. Thank you for your contributions.

@stale stale bot closed this Jun 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
do-not-merge stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@snyk-bot