CVE Vulnerabilities

CVE-2021-32719

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

Published: Jun 28, 2021 | Modified: Nov 21, 2024
CVSS 3.x
4.8
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
CVSS 2.x
3.5 LOW
AV:N/AC:M/Au:S/C:N/I:P/A:N
RedHat/V2
RedHat/V3
4.8 LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
Ubuntu
LOW

RabbitMQ is a multi-protocol messaging broker. In rabbitmq-server prior to version 3.8.18, when a federation link was displayed in the RabbitMQ management UI via the rabbitmq_federation_management plugin, its consumer tag was rendered without proper tag sanitization. This potentially allows for JavaScript code execution in the context of the page. The user must be signed in and have elevated permissions (manage federation upstreams and policies) for this to occur. The vulnerability is patched in RabbitMQ 3.8.18. As a workaround, disable the rabbitmq_federation_management plugin and use CLI tools instead.

Weakness

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as “<”, “>”, and “&” that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.

Affected Software

Name Vendor Start Version End Version
Rabbitmq Vmware * 3.8.18 (excluding)
Red Hat OpenStack Platform 16.2 RedHat rabbitmq-server-0:3.8.16-3.el8ost *
Rabbitmq-server Ubuntu bionic *
Rabbitmq-server Ubuntu focal *
Rabbitmq-server Ubuntu groovy *
Rabbitmq-server Ubuntu hirsute *
Rabbitmq-server Ubuntu impish *
Rabbitmq-server Ubuntu trusty *
Rabbitmq-server Ubuntu upstream *
Rabbitmq-server Ubuntu xenial *

Potential Mitigations

  • Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.
  • The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.

References