# CVE-2023-35789: Information disclosure in n/a > Local attackers can read RabbitMQ credentials from command-line arguments in the C AMQP client library. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Jun 2023 - **Updated:** 30 Mar 2025 - **Also known as:** ALPINE-CVE-2023-35789, ALSA-2023:6482, ALSA-2023:7150, AZL-43804, AZL-45114, BELL-CVE-2023-35789, BIT-rabbitmq-c-2023-35789, DEBIAN-CVE-2023-35789, DLA-4096-1, GHSA-cj9f-gcwh-7q49, OESA-2023-1399, RHSA-2023:6482, RHSA-2023:7150, RLSA-2023:6482, ROOT-OS-ALPINE-318-CVE-2023-35789, SUSE-SU-2023:2823-1, UBUNTU-CVE-2023-35789, openSUSE-SU-2024:13028-1 ## What is CVE-2023-35789? CVE-2023-35789 is a medium-severity vulnerability in n/a, published on 16 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description An issue was discovered in the C AMQP client library (aka rabbitmq-c) through 0.13.0 for RabbitMQ. Credentials can only be entered on the command line (e.g., for amqp-publish or amqp-consume) and are thus visible to local attackers by listing a process and its arguments. Weakness: CWE-522 (Insufficiently Protected Credentials) ## Which versions are affected by CVE-2023-35789? 1 open source package ship an affected version, including rabbitmq-c. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `rabbitmq-c` | Bitnami | All versions to 0.13.0 | None | | `librabbitmq` | AlmaLinux:8 | All versions | 0.9.0-4.el8 | | `librabbitmq-devel` | AlmaLinux:8 | All versions | 0.9.0-4.el8 | | `librabbitmq` | AlmaLinux:9 | All versions | 0.11.0-7.el9 | | `librabbitmq-devel` | AlmaLinux:9 | All versions | 0.11.0-7.el9 | | `librabbitmq-tools` | AlmaLinux:9 | All versions | 0.11.0-7.el9 | | `librabbitmq` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.9.0-4.el8 | | `librabbitmq-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.9.0-4.el8 | | `librabbitmq-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.9.0-4.el8 | | `librabbitmq-tools-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.9.0-4.el8 | | `librabbitmq-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.9.0-4.el8 | | `librabbitmq-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.9.0-4.el8 | | `librabbitmq-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.9.0-4.el8 | | `librabbitmq-tools-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.9.0-4.el8 | | `librabbitmq` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.11.0-7.el9 | | `librabbitmq-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.11.0-7.el9 | | `librabbitmq-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.11.0-7.el9 | | `librabbitmq-tools` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.11.0-7.el9 | | `librabbitmq-tools-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.11.0-7.el9 | | `librabbitmq-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:0.11.0-7.el9 | | `librabbitmq-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:0.11.0-7.el9 | | `librabbitmq-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:0.11.0-7.el9 | | `librabbitmq-tools-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:0.11.0-7.el9 | | `librabbitmq` | Rocky Linux:9 | All versions | 0:0.11.0-7.el9 | | `rabbitmq-c` | SUSE:Enterprise Storage 7.1 | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | SUSE:Linux Enterprise Module for Server Applications 15 SP4 | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | SUSE:Linux Enterprise Module for Server Applications 15 SP5 | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | SUSE:Manager Proxy 4.2 | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | SUSE:Manager Server 4.2 | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | openSUSE:Leap 15.4 | All versions | 0.10.0-150300.5.6.1 | | `rabbitmq-c` | openSUSE:Leap 15.5 | All versions | 0.10.0-150300.5.6.1 | Products: Rabbitmq-C Project Rabbitmq-C. ## How do I fix CVE-2023-35789? Apply the vendor's patch. ## Is CVE-2023-35789 being exploited? There is no known exploitation of CVE-2023-35789 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-35789 and fix it if it is affected. What it is: CVE-2023-35789 is a medium-severity vulnerability in n/a, published on 16 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-35789 in the wild and no public exploit code. Affected packages and fixed versions: - rabbitmq-c (Bitnami): affected all versions up to 0.13.0; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-35789/ (Markdown: https://insights.sbomify.com/CVE-2023-35789/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-35789 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-35789 - OSV: https://osv.dev/vulnerability/CVE-2023-35789 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-35789/ Summaries are generated and may contain mistakes; the official description above is the record.