- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202003-07
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: High
    Title: RabbitMQ C client: Arbitrary code execution
     Date: March 13, 2020
     Bugs: #701810
       ID: 202003-07

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
=======
A vulnerability in RabbitMQ C client might allow an attacker to execute
arbitrary code.

Background
=========
A C-language AMQP client library for use with v2.0+ of the RabbitMQ
broker.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  net-libs/rabbitmq-c          < 0.10.0                  >= 0.10.0

Description
==========
It was discovered that RabbitMQ C client incorrectly handled certain
inputs.

Impact
=====
A remote attacker, by sending a specially crafted request, could
possibly execute arbitrary code with the privileges of the process or
cause a Denial of Service condition.

Workaround
=========
There is no known workaround at this time.

Resolution
=========
All RabbitMQ C client users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-libs/rabbitmq-c-0.10.0"

References
=========
[ 1 ] CVE-2019-18609
      https://nvd.nist.gov/vuln/detail/CVE-2019-18609

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202003-07

Concerns?
========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
======
Copyright 2020 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-202003-07: RabbitMQ C client: Arbitrary code execution

A vulnerability in RabbitMQ C client might allow an attacker to execute arbitrary code.

Summary

It was discovered that RabbitMQ C client incorrectly handled certain inputs.

Resolution

All RabbitMQ C client users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=net-libs/rabbitmq-c-0.10.0"

References

[ 1 ] CVE-2019-18609 https://nvd.nist.gov/vuln/detail/CVE-2019-18609

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202003-07

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: High
Title: RabbitMQ C client: Arbitrary code execution
Date: March 13, 2020
Bugs: #701810
ID: 202003-07

Synopsis

A vulnerability in RabbitMQ C client might allow an attacker to execute arbitrary code.

Background

A C-language AMQP client library for use with v2.0+ of the RabbitMQ broker.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-libs/rabbitmq-c < 0.10.0 >= 0.10.0

Impact

===== A remote attacker, by sending a specially crafted request, could possibly execute arbitrary code with the privileges of the process or cause a Denial of Service condition.

Workaround

There is no known workaround at this time.

Related News