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

chore(package): Update dependency sapper to 0.27.11 [SECURITY] #16

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 28, 2020

Mend Renovate

This PR contains the following updates:

Package Change
sapper 0.25.0 -> 0.27.11

GitHub Vulnerability Alerts

GHSA-f3vw-587g-r29g

Versions of sapper prior to 0.27.11 are vulnerable to Path Traversal. It is possible to access sensitive files on the server through HTTP requests containing URL-encoded ../.

You may test a sapper application running in prod mode with curl -vvv http://localhost:3000/client/750af05c3a69ddc6073a/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/etc/passwd.

Recommendation

Upgrade to version 0.27.11 or later.


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

@renovate
Copy link
Contributor Author

renovate bot commented Nov 28, 2020

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/npm-sapper-vulnerability branch from b3c13e2 to ee3ac30 Compare February 11, 2021 10:10
@renovate renovate bot force-pushed the renovate/npm-sapper-vulnerability branch from ee3ac30 to dc4f412 Compare February 22, 2021 12:17
@renovate renovate bot changed the title chore(package): Update dependency sapper to ^0.27.0 [SECURITY] chore(package): Update dependency sapper to ^0.27.11 [SECURITY] Feb 22, 2021
@renovate renovate bot force-pushed the renovate/npm-sapper-vulnerability branch from dc4f412 to 1309a95 Compare February 25, 2021 12:45
@renovate renovate bot changed the title chore(package): Update dependency sapper to ^0.27.11 [SECURITY] chore(package): Update dependency sapper to ^0.27.0 [SECURITY] Feb 25, 2021
@renovate renovate bot changed the title chore(package): Update dependency sapper to ^0.27.0 [SECURITY] chore(package): Update dependency sapper to 0.27.11 [SECURITY] Mar 4, 2021
@renovate renovate bot changed the title chore(package): Update dependency sapper to 0.27.11 [SECURITY] chore(package): Update dependency sapper to 0.27.11 [SECURITY] - autoclosed Jun 10, 2021
@renovate renovate bot closed this Jun 10, 2021
@renovate renovate bot deleted the renovate/npm-sapper-vulnerability branch June 10, 2021 02:44
@renovate renovate bot changed the title chore(package): Update dependency sapper to 0.27.11 [SECURITY] - autoclosed chore(package): Update dependency sapper to 0.27.11 [SECURITY] Jun 10, 2021
@renovate renovate bot reopened this Jun 10, 2021
@renovate renovate bot restored the renovate/npm-sapper-vulnerability branch June 10, 2021 03:52
@renovate renovate bot force-pushed the renovate/npm-sapper-vulnerability branch from 1309a95 to 6e39c05 Compare June 10, 2021 04:04
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

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.

None yet

1 participant