Information Exposure Through Log Files Affecting rabbitmq-server313-bash-completion package, versions <3.13.1-150600.13.11.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.02% (4th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Information Exposure Through Log Files vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-SLES157-RABBITMQSERVER313BASHCOMPLETION-12818357
  • published17 Sept 2025
  • disclosed15 Sept 2025

Introduced: 15 Sep 2025

NewCVE-2025-50200  (opens in a new tab)
CWE-532  (opens in a new tab)

How to fix?

Upgrade SLES:15.7 rabbitmq-server313-bash-completion to version 3.13.1-150600.13.11.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rabbitmq-server313-bash-completion package and not the rabbitmq-server313-bash-completion package as distributed by SLES. See How to fix? for SLES:15.7 relevant fixed versions and status.

RabbitMQ is a messaging and streaming broker. In versions 3.13.7 and prior, RabbitMQ is logging authorization headers in plaintext encoded in base64. When querying RabbitMQ api with HTTP/s with basic authentication it creates logs with all headers in request, including authorization headers which show base64 encoded username:password. This is easy to decode and afterwards could be used to obtain control to the system depending on credentials. This issue has been patched in version 4.0.8.

CVSS Base Scores

version 3.1