This repository was archived by the owner on Feb 6, 2025. It is now read-only.
fix(deps): update dependency @fastify/reply-from to v9.6.0 [security] #699
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@fastify/[email protected] |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
9.4.0->9.6.0GitHub Vulnerability Alerts
CVE-2023-51701
Impact
The main repo of fastify use fast-content-type-parse to parse request Content-Type, which will trim after split.
The fastify-reply-from have not use this repo to unify the parse of Content-Type, which won't trim.
As a result, a reverse proxy server built with
@fastify/reply-fromcould misinterpret the incoming body by passing an headerContentType: application/json ; charset=utf-8. This can lead to bypass of security checks.Patches
@fastify/reply-fromv9.6.0 include the fix.Workarounds
There are no known workarounds.
References
Hackerone Report: https://hackerone.com/reports/2295770.
Release Notes
fastify/fastify-reply-from (@fastify/reply-from)
v9.6.0Compare Source
Fixes CVE-2023-51701, see GHSA-v2v2-hph8-q5xp for more details. Severity: moderate.
Full Changelog: fastify/fastify-reply-from@v9.5.0...v9.6.0
v9.5.0Compare Source
What's Changed
node:prefix to bypass require.cache call for builtins by @Fdawgs in https://github.com/fastify/fastify-reply-from/pull/324.gitattributesfile by @Fdawgs in https://github.com/fastify/fastify-reply-from/pull/327use strictdirective by @Fdawgs in https://github.com/fastify/fastify-reply-from/pull/329New Contributors
Full Changelog: fastify/fastify-reply-from@v4.18.0...v9.5.0
Configuration
📅 Schedule: Branch creation - "" in timezone Africa/Johannesburg, 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.
This PR was generated by Mend Renovate. View the repository job log.