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 #94

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

Conversation

ekmixon
Copy link
Owner

@ekmixon ekmixon commented Dec 1, 2023

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:
    • src/pybind/mgr/dashboard/frontend/package.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
Yes No Known Exploit

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

Commit messages
Package name: @compodoc/compodoc The new version differs by 215 commits.
  • ffe8abb 1.1.14
  • 3cd09ba 1.1.14
  • 9bb5772 1.1.14
  • c65504e fix(app): correct supports ArrayType and tuples
  • 0e02e05 fix(app): correct supports ArrayType
  • d6d9955 fix(app): tuple types
  • 162ea28 fix(app): union type and literaltypenode
  • 4a6ad03 fix(app): union type and literaltypenode
  • 47fe06d fix(app): rawDescription for JSDoc and visitEnumTypeAliasFunctionDeclarationDescription
  • a888f25 fix(app): rawDescription for JSDoc and visitEnumTypeAliasFunctionDeclarationDescription
  • 0bb000d fix(app): rawDescription for JSDoc and visitInputAndHostBinding
  • f698d96 feat(github): new ISSUE_TEMPLATE
  • 809432e feat(github): new ISSUE_TEMPLATE
  • 95073c3 Update issue templates
  • f4ac68c feat(github): new ISSUE_TEMPLATE
  • 9713982 feat(github): new ISSUE_TEMPLATE
  • c2a69c9 feat(github): new ISSUE_TEMPLATE
  • d8722c2 feat(github): new ISSUE_TEMPLATE
  • 125641b fix(app): rawDescription for JSDoc and variables
  • c1282d2 fix(app): support for Type Reference and template literal
  • 9c180f5 fix(app): drop usage of ts-simple-ast for ts-morph
  • 7bb9a40 fix(app): drop usage of ts-simple-ast for ts-morph
  • ee0d9c3 fix(app): support for Type Reference / WIP
  • 0c7a052 fix(theme): dark mode support

See the full diff

Package name: jest The new version differs by 250 commits.

See the full diff

Package name: stylelint-declaration-use-variable The new version differs by 13 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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Copy link

guardrails bot commented Dec 1, 2023

⚠️ We detected 6 security issues in this pull request:

Vulnerable Libraries (6)
Severity Details
Critical pkg:npm/jest@26.5.2 (t) upgrade to: > 26.5.2
Critical pkg:npm/@angular/localize@10.1.5 (t) upgrade to: > 10.1.5
Critical pkg:npm/@compodoc/compodoc@1.1.11 (t) upgrade to: > 1.1.11
Critical pkg:npm/stylelint-declaration-use-variable@1.7.2 (t) upgrade to: > 1.7.2
Critical pkg:npm/@angular/cli@10.1.6 (t) upgrade to: > 10.1.6
Critical pkg:npm/@angular-devkit/build-angular@0.1002.3 (t) upgrade to: > 0.1002.3

More info on how to fix Vulnerable Libraries in JavaScript.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

Micro-Learning Topic: Vulnerable library (Detected by phrase)

Matched on "Vulnerable Libraries"

What is this? (2min video)

Use of vulnerable components will introduce weaknesses into the application. Components with published vulnerabilities will allow easy exploitation as resources will often be available to automate the process.

Try a challenge in Secure Code Warrior

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