Lucene search

K
redhatRedHatRHSA-2013:1024
HistoryJul 11, 2013 - 12:00 a.m.

(RHSA-2013:1024) Moderate: Red Hat Enterprise MRG Messaging 2.3.3 security update

2013-07-1100:00:00
access.redhat.com
22

EPSS

0.001

Percentile

31.4%

Red Hat Enterprise MRG (Messaging, Realtime, and Grid) is a next-generation
IT infrastructure for enterprise computing. MRG offers increased
performance, reliability, interoperability, and faster computing for
enterprise customers.

MRG Messaging is a high-speed reliable messaging distribution for Linux
based on AMQP (Advanced Message Queuing Protocol), an open protocol
standard for enterprise messaging that is designed to make mission critical
messaging widely available as a standard service, and to make enterprise
messaging interoperable across platforms, programming languages, and
vendors. MRG Messaging includes an AMQP 0-10 messaging broker; AMQP 0-10
client libraries for C++, Java JMS, and Python; as well as persistence
libraries and management tools.

It was discovered that the Qpid Python client library for AMQP did not
properly perform TLS/SSL certificate validation of the remote server’s
certificate, even when the ‘ssl_trustfile’ connection option was specified.
A rogue server could use this flaw to conduct man-in-the-middle attacks,
possibly leading to the disclosure of sensitive information.
(CVE-2013-1909)

With this update, Python programs can instruct the library to validate
server certificates by specifying a path to a file containing trusted CA
certificates.

This issue was discovered by Petr Matousek of the Red Hat MRG Messaging
team.

This update also fixes multiple bugs. Documentation for these changes will
be available shortly from the Technical Notes document linked to in the
References section.

All users of the Messaging capabilities of Red Hat Enterprise MRG 2.3 are
advised to upgrade to these updated packages, which resolve the issues
noted in the Red Hat Enterprise MRG 2 Technical Notes. After installing the
updated packages, stop the cluster by either running “service qpidd stop”
on all nodes, or “qpid-cluster --all-stop” on any one of the cluster nodes.
Once stopped, restart the cluster with “service qpidd start” on all nodes
for the update to take effect.

EPSS

0.001

Percentile

31.4%