Bug 1174872 (CVE-2014-9494) - CVE-2014-9494 rabbitmq-server: insufficient 'X-Forwarded-For' header validation
Summary: CVE-2014-9494 rabbitmq-server: insufficient 'X-Forwarded-For' header validation
Keywords:
Status: NEW
Alias: CVE-2014-9494
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1174874 1174875 1174876
Blocks: 1174877
TreeView+ depends on / blocked
 
Reported: 2014-12-16 16:17 UTC by Martin Prpič
Modified: 2019-09-29 13:25 UTC (History)
22 users (show)

Fixed In Version: RabbitMQ 3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Martin Prpič 2014-12-16 16:17:25 UTC
In RabbitMQ, the 'loopback_users' configuration directive allows to specify a list of users that are only permitted to connect to the broker via localhost. It was found that the RabbitMQ's management plug-in did not sufficiently validate the 'X-Forwarded-For' header when determining the remote address. A remote attacker able to send a specially crafted 'X-Forwarded-For' header to RabbitMQ could use this flaw to connect to the broker as if they were a localhost user. Note that the attacker must know valid user credentials in order to connect to the broker.

Upstream patches:

http://hg.rabbitmq.com/rabbitmq-management/rev/c3c41177a11a
http://hg.rabbitmq.com/rabbitmq-management/rev/35e916df027d

References:

https://groups.google.com/forum/#!topic/rabbitmq-users/DMkypbSvIyM
http://www.rabbitmq.com/release-notes/README-3.4.0.txt

Comment 1 Martin Prpič 2014-12-16 16:18:10 UTC
Created rabbitmq-server tracking bugs for this issue:

Affects: fedora-all [bug 1174874]
Affects: epel-all [bug 1174875]
Affects: epel-all [bug 1174876]

Comment 2 Fedora Update System 2015-01-06 02:09:11 UTC
rabbitmq-server-3.3.5-4.el7 has been pushed to the Fedora EPEL 7 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.