grpc is vulnerable to Incorrect Authorization
76
CVE Score
High
Incorrect Authorization
Only the HTTP transcoding clause of GRPC.Server.do_handle_request/4 copies path bindings into the request message. A request to a transcoded URL with a gRPC Content-Type is decoded from the body alone, so a path-bound field takes the body value instead of the URL. The fix applies path bindings for gRPC content types on transcoded routes.
Upgrade the grpc library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and enable HTTP transcoding with http_transcode: true.
0.8.0 - 0.11.5
Fixed in 1.0.0grpc is vulnerable to Incorrect Authorization in versions 0.8.0 - 0.11.5.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.