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

fix(deps): update dependency @backstage/backend-common to v0.20.2 [security] #252

Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 23, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@backstage/backend-common (source) 0.20.1 -> 0.20.2 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-26150

Impact

Paths checks with the resolveSafeChildPath utility were not exhaustive enough, leading to risk of path traversal vulnerabilities if symlinks can be injected by attackers.

Patches

Patched in @backstage/backend-common version 0.21.1.
Patched in @backstage/backend-common version 0.20.2.
Patched in @backstage/backend-common version 0.19.10.

For more information

If you have any questions or comments about this advisory:


Release Notes

backstage/backstage (@​backstage/backend-common)

v0.20.2

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@jvilimek jvilimek merged commit 163bea6 into main Apr 9, 2024
3 checks passed
@renovate renovate bot deleted the renovate/npm-@backstage/backend-common-vulnerability branch April 9, 2024 15:16
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.

None yet

1 participant