gRPC
— gRPC Remote Procedure CallgRPC enables client applications to directly call methods on a server application on a different machine as if it were a local object. By combining strongly typed Protocol Buffers (Protobuf) serialization with HTTP/2 multiplexed streaming, gRPC delivers up to 10x faster performance than traditional JSON REST APIs.
Interactive Session: How gRPC Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of gRPC.
Threat Model & Attack Simulation
How this protocol is attacked in practice, what defenders can see, and which control stops it.
Threat model & attack simulation
SimulatedDefensive education. Every step runs in this page; no traffic is generated or sent.
Reflection-enabled method abuse
Feature abuseServer reflection and missing authorisation expose RPC methods that clients were never meant to call directly.
List the services
The attacker enables reflection and enumerates methods and message types.
Reflection requests from an unexpected client.
Unauthorised data access and privileged operations.
Defences that matter
- Disable reflection in production
- Per-method authorisation and scopes
- Validate and sign caller metadata
This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.
Protocol Specification & Architecture
Key characteristics, real-world deployment patterns, and trade-offs.
Core Technical Features
- Compact binary serialization via Protocol Buffers (.proto schemas)
- Built natively on HTTP/2 transport with bidirectional streaming
- Strongly typed contracts with auto-generated client SDKs across 10+ languages
- Built-in deadline propagation, cancellation, and metadata headers
Real-World Use Cases
- High-throughput microservices internal communication
- Low-latency mobile app backends
- Cloud-native Kubernetes service mesh (Envoy)
Advantages & Strengths
- Much faster and smaller payloads than JSON REST
- Native support for client/server/bidirectional streaming
Limitations & Vulnerabilities
- Binary payloads are not directly human-readable in standard browser devtools
- Requires gRPC-Web proxy for standard browser support