rabbitmq-c -- remote client-side memory exhaustion

The rabbitmq-c project reports:

A malicious AMQP peer can trigger memory exhaustion in rabbitmq-c clients by sending frames with unrecognised types or invalid channel numbers. The client allocates per-channel memory pools and stores complete frames before validating the channel against the negotiated limits or the frame type, and discards unknown frames without releasing that memory, allowing a sustained stream of small frames to exhaust client resources.

[source]