{"uuid": "9cff29d5-e329-4bf0-b397-4088b69c6647", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-50200", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18869", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-50200\n\ud83d\udd25 CVSS Score: 6.7 (cvssV4_0, Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2025-06-19T16:14:24.919Z\n\ud83d\udccf Modified: 2025-06-19T16:14:24.919Z\n\ud83d\udd17 References:\n1. https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-gh3x-4x42-fvq8", "creation_timestamp": "2025-06-19T16:45:41.000000Z"}