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] Security upgrade uplot from 1.6.26 to 1.6.31 #6164

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

Conversation

ankitnayan
Copy link
Collaborator

@ankitnayan ankitnayan commented Oct 11, 2024

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

Changes included in this PR

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

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 619/1000
Why? Proof of Concept exploit, Recently disclosed, CVSS 8.8
Prototype Pollution
SNYK-JS-UPLOT-6209224
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:

🦉 Prototype Pollution


Important

Upgrade uplot to 1.6.31 to fix a high-severity prototype pollution vulnerability.

  • Dependencies:
    • Upgrade uplot from 1.6.26 to 1.6.31 in frontend/package.json and frontend/yarn.lock to fix a prototype pollution vulnerability.
  • Security:
    • Addresses high-severity vulnerability SNYK-JS-UPLOT-6209224 with a CVSS score of 8.8.

This description was created by Ellipsis for 9279999. It will automatically update as commits are pushed.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Reviewed everything up to 9279999 in 10 seconds

More details
  • Looked at 13 lines of code in 1 files
  • Skipped 1 files when reviewing.
  • Skipped posting 2 drafted comments based on config settings.
1. frontend/package.json:126
  • Draft comment:
    Ensure that the updated version of 'uplot' (1.6.31) is compatible with the rest of the dependencies and the project's requirements.
  • Reason this comment was not posted:
    Confidence changes required: 50%
    The PR updates the version of 'uplot' in package.json. I need to ensure that the change is consistent and correct.
2. frontend/package.json:126
  • Draft comment:
    No issues found related to the rules provided.
  • Reason this comment was not posted:
    Confidence changes required: 0%
    The package.json file looks fine, no issues related to the rules provided.

Workflow ID: wflow_HU7xRj2uh8LLUl4y


You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

Copy link

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

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

Successfully merging this pull request may close these issues.

4 participants