RabbitMQ versions prior to 4.2.7 and 4.3.1 contain a vulnerability where an authenticated AMQP client can cause atom-table exhaustion by sending specially crafted reply-to queue names. This leads to the creation of atoms that are never garbage collected, resulting in a crash of the entire Erlang VM hosting RabbitMQ. The issue is fixed in versions 4.2.7 and 4.3.1.