Skip to content

[Snyk] Fix for 1 vulnerabilities#4337

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-dcb8761439d31a146e8c6c6268785673
Closed

[Snyk] Fix for 1 vulnerabilities#4337
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-dcb8761439d31a146e8c6c6268785673

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Mar 28, 2025

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • plugins/catalog-backend-module-ldap/package.json

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.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Symlink Attack
SNYK-JS-TARFS-9535930
  721  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

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

Summary by Sourcery

Update package dependencies to fix a high-severity security vulnerability in the LDAP catalog backend module

Bug Fixes:

  • Fix a high-severity Symlink Attack vulnerability (SNYK-JS-TARFS-9535930) by updating package dependencies

Enhancements:

  • Update package dependencies from workspace references to specific versions

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Mar 28, 2025

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@restack-app
Copy link
Copy Markdown

restack-app Bot commented Mar 28, 2025

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Mar 28, 2025

Reviewer's Guide by Sourcery

This pull request updates several @backstage dependencies in plugins/catalog-backend-module-ldap/package.json to address a reported security vulnerability. The versions of @backstage/backend-tasks, @backstage/catalog-model, @backstage/plugin-catalog-common, and @backstage/plugin-catalog-node have been updated from workspace:^ to specific versions.

Updated class diagram for package.json dependencies

classDiagram
  class PackageJson {
    dependencies
  }

  PackageJson --|> Dependency

  class Dependency {
    +string @backstage/backend-tasks
    +string @backstage/catalog-model
    +string @backstage/plugin-catalog-common
    +string @backstage/plugin-catalog-node
    +string @backstage/config
    +string @backstage/errors
    +string @backstage/types
    +string ldapjs
    +string uuid
    +string @types/ldapjs
  }

  note for Dependency "Dependencies versions have been updated to address a security vulnerability."
Loading

File-Level Changes

Change Details Files
Updated multiple @backstage dependencies to address a security vulnerability.
  • Updated @backstage/backend-tasks from workspace:^ to 0.6.1.
  • Updated @backstage/catalog-model from workspace:^ to 0.1.1.
  • Updated @backstage/plugin-catalog-common from workspace:^ to 0.1.0.
  • Updated @backstage/plugin-catalog-node from workspace:^ to 1.0.0.
plugins/catalog-backend-module-ldap/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot (hey, snyk-io[bot]!). We assume it knows what it's doing!
  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 4, 2025

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Apr 4, 2025
Comment on lines +35 to +40
"@backstage/backend-tasks": "0.6.1",
"@backstage/catalog-model": "0.1.1",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/plugin-catalog-node": "workspace:^",
"@backstage/plugin-catalog-common": "0.1.0",
"@backstage/plugin-catalog-node": "1.0.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The version numbers specified in this PR appear problematic and may introduce compatibility issues:

  1. The versions being introduced (catalog-model@0.1.1, plugin-catalog-common@0.1.0) seem to be extremely old, while plugin-catalog-node is set to 1.0.0.

  2. These packages are typically interdependent, and such version mismatches could cause runtime errors or unexpected behavior.

  3. The PR description notes a failure to update the yarn.lock file, which is a red flag that these dependency changes haven't been properly resolved.

Before merging, it would be advisable to:

  • Verify these are the correct target versions for addressing the vulnerability
  • Ensure all interdependent packages are updated to compatible versions
  • Successfully update the yarn.lock file to confirm dependency resolution
Suggested change
"@backstage/backend-tasks": "0.6.1",
"@backstage/catalog-model": "0.1.1",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/plugin-catalog-node": "workspace:^",
"@backstage/plugin-catalog-common": "0.1.0",
"@backstage/plugin-catalog-node": "1.0.0",
"@backstage/backend-tasks": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/plugin-catalog-node": "workspace:^",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

@github-actions github-actions Bot removed the stale label Apr 4, 2025
@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Apr 11, 2025
@github-actions github-actions Bot closed this Apr 16, 2025
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.

0 participants