fix(nextjs): Strictly validate tunnel target parameters#9415
Merged
Conversation
Contributor
size-limit report 📦
|
mydea
approved these changes
Oct 31, 2023
|
🍿 |
|
Is it obvious what the impact of this is? Are there any attackers utilising this in the wild? I understand it is probably not a great design choice and the validation should have been stronger, but it would be great to get an idea of exposure |
Contributor
|
@hueypeard this was published earlier today: https://blog.sentry.io/next-js-sdk-security-advisory-cve-2023-46729/ |
Contributor
Author
|
@hueypeard Seconding what @sreetamdas mentioned. We wrote up an FAQ with everything we could think of that might be relevant to the vulnerability. If you're still missing information, let us know how we can improve it! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
No description provided.