fix(sidecar) : quarkus platform version update & graphql vulnerability fixed #17
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.
Subject: fix(sidecar) : quarkus platform version update & graphql vulnerability fixed
Assignees: @soumyadip007
Issue
A flaw was found in Quarkus. This issue occurs when receiving a request over websocket with no role-based permission specified on the GraphQL operation, Quarkus processes the request without authentication despite the endpoint being secured. This can allow an attacker to access information and functionality outside of normal granted API permissions. (CVE Details)
Resolution (Reason behind the version update)
Quarkus team has resolve the GraphQL Websocket in their recent release (Quarkus 3.5.3). The have also resolved few of the issues in their latest version so we're updating the Quarkus platform version to 3.6.4.