[Aikido] Fix security issue in undici via minor version upgrade from 6.25.0 to 6.27.0 in with-react-native#38
Merged
Conversation
|
Dependency limit exceeded — report not shown. This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report. Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard. Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account. |
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
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.
Upgrade undici to fix WebSocket DoS vulnerability allowing unbounded memory growth through fragment flooding.
All breaking changes by upgrading undici from version 6.25.0 to 6.27.0 (CHANGELOG)
parseSetCookieno longer applies percent-decoding to cookie values, changing behavior for encoded sequences like%0D%0Aand%00which were previously decoded into literal bytes but are now preserved as-is per RFC 6265 §5.4SameSitecookie attribute parsing now requires exact matches (Strict,Lax, orNone) instead of accepting these values as substrings, rejecting previously accepted values likeSameSite=NoneOfYourBusinessorSameSite=StrictLax✅ 1 CVE resolved by this upgrade
This PR will resolve the following CVEs:
Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.