[Aikido] Fix 36 security issues in hono, fast-uri#6
Open
aikido-autofix[bot] wants to merge 1 commit into
Open
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
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 Hono and fast-uri to fix path traversal, CORS credential bypass, and URI normalization bypass vulnerabilities.
✅ Code not affected by breaking changes.
✅ No breaking changes affect this codebase. The
fast-uripackage is only used as a transitive dependency throughajv, which is used by theconfpackage. However, theConfinstance inapps/cli/src/config/store.tsis created without any schema validation (noschemaoption is passed). Since the breaking change only affects URI fragment parsing during JSON schema validation, and this codebase doesn't use schema validation withconf, the upgrade will not cause any issues.All breaking changes by upgrading fast-uri from version 3.1.0 to 3.1.3 (CHANGELOG)
✅ 36 CVEs resolved by this upgrade
This PR will resolve the following CVEs:
Content-Lengthwas missing or bodies were chunked, due to asynchronous limit enforcement. This could enable DoS attacks or unintended data processing despite configured size restrictions.setCookie(),serialize(), orserializeSigned(), allowing invalid characters that can cause malformed Set-Cookie headers and runtime errors when processing untrusted cookie names.parseBody({ dot: true })where specially crafted form field names like__proto__.xcreate objects with__proto__properties, potentially enabling prototype pollution if merged unsafely into other objects.jsx()andcreateElement(), allowing untrusted tag input to inject markup and reshape generated HTML, potentially enabling XSS attacks.