The workflow:

• Client of gRPC decoder configure the max_frame_length via setMaxFrameLength()
• At beginning of gRPC frame decoding process ( before frameDataStart()), total length of the frame is determined.
• If max_frame_length is configured and total length exceeds the limit, the decoding process which includes excessive data addition/storage (i.e. frameData()) will be skipped and returned.

The use case/ motivation: Enable max_receive_message_length in Envoy-gRPC (which use gRPC decoder) .

• When the message is over limit, it can be rejected before frame data is fully decoded (i.e. expanded).
• This can prevent malicious attack , for example, unbounded and huge message is sent over channel and is injected and buffered in Envoy over Envoy-gRPC.

Next step:

• Refactor bool Decoder::decode method: Change the return type from bool to absl:status so that the caller can identify whether it is decoding error or over-limit error.

Request variables

Key	Value
ref	f14caf2a4cdef4c2e91ce45548ca47de5c396494
sha	1723bff
pr	32511
base-sha	6231a64
actor	@tyxia
message	grpc: Add support for max frame length in gPRC frame decoding...
started	1709356088.564294
target-branch	main
trusted	false

Container image/s (as used in this CI run)

Envoy version (as used in this CI run)