oss-sec mailing list archives
Re: CVE request: insufficient 'X-Forwarded-For' header validation in rabbitmq-server
From: cve-assign () mitre org
Date: Sat, 3 Jan 2015 19:03:12 -0500 (EST)
""" RabbitMQ 3.3.0 introduced a mechanism (the 'loopback_users' configuration item) allowing access for some users to be restricted to only connect via localhost. By default the "guest" user is restricted in this way. Unfortunately, the HTTP framework used by the management plugin trusts the easily-forged "X-Forwarded-For" header when determining the remote address. It is therefore possible to subvert this access control mechanism for the HTTP API. Attackers would still need to know or guess the username and password. """ 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 https://bugzilla.redhat.com/show_bug.cgi?id=1174872
Use CVE-2014-9494. --- CVE assignment team, MITRE CVE Numbering Authority M/S M300 202 Burlington Road, Bedford, MA 01730 USA [ PGP key available through http://cve.mitre.org/cve/request_id.html ]
Current thread:
- Re: CVE request: insufficient 'X-Forwarded-For' header validation in rabbitmq-server cve-assign (Jan 03)