Am I affected?

type your grpc version to check

Description

Authorization Bypass Through User-Controlled Key vulnerability in elixir-grpc grpc allows authenticated attackers to access or modify resources belonging to other users by smuggling a conflicting value for any path-bound field via the query string or request body.

In 'Elixir.GRPC.Server.Transcode':map_request/5 (lib/grpc/server/transcode.ex), all three clauses use Map.merge/2 with path bindings as the first argument, giving them the lowest merge precedence. A request such as GET /users/me/profile?user_id=victim (or a POST with {"user_id": "victim"} when body: "*") yields a decoded protobuf struct where the path-bound field carries the attacker-supplied value rather than the router-extracted value. Any handler that uses the path-bound field for authorization, multi-tenancy scoping, or ownership checks is silently bypassed.

This issue affects grpc from 0.8.0 before 1.0.0.

Weaknesses & attack patterns

Weakness

CWE-639 · Authorization Bypass Through User-Controlled Key in catalog → MITRE ↗

Attack patterns

CAPEC-460 · HTTP Parameter Pollution (HPP) MITRE ↗

Affected — Hex / grpc Hex.pm ↗ Repository ↗

0.8.0 < 1.0.0 affected
every other version: unaffected
cpe cpe:2.3:a:elixir-grpc:grpc:*:*:*:*:*:*:*:*
modules · source files · routines
modules 'Elixir.GRPC.Server.Transcode'
source files lib/grpc/server/transcode.ex
routines 'Elixir.GRPC.Server.Transcode':map_request/5

Affected — GitHub / elixir-grpc/grpc Repository ↗

8aaf3d3 < 33b6a09 affected
every other version: unaffected
cpe cpe:2.3:a:elixir-grpc:grpc:*:*:*:*:*:*:*:*
modules · source files · routines
modules 'Elixir.GRPC.Server.Transcode'
source files lib/grpc/server/transcode.ex
routines 'Elixir.GRPC.Server.Transcode':map_request/5

Configurations

HTTP-to-gRPC transcoding must be enabled.

References

Credits

Peter Ullrich Finder
Paulo Valente Remediation developer
Jonatan Männchen Analyst

CVSS breakdown

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
« All CVEs