# CVE-2024-4840: Rhosp-director: cleartext passwords exposed in logs

> Attackers with log access can read plaintext passwords exposed by the OpenStack director, compromising sensitive credentials.

- **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:** 13 May 2024
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-m73w-f4gh-h9g2, RHSA-2024:9978

## What is CVE-2024-4840?

CVE-2024-4840 is a medium-severity vulnerability in Red Hat OpenStack Platform 16.2, published on 13 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An flaw was found in the OpenStack Platform (RHOSP) director, a toolset for installing and managing a complete RHOSP environment. Plaintext passwords may be stored in log files, which can expose sensitive information to anyone with access to the logs.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2024-4840?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-tripleo-heat-templates` | Red Hat:openstack:17.1::el9 | All versions | 0:14.3.1-17.1.20240919130756.el9ost |

## How do I fix CVE-2024-4840?

Apply the vendor's patch.

## Is CVE-2024-4840 being exploited?

There is no known exploitation of CVE-2024-4840 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4840 and fix it if it is affected.

What it is: CVE-2024-4840 is a medium-severity vulnerability in Red Hat OpenStack Platform 16.2, published on 13 May 2024. 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-2024-4840 in the wild and no public exploit code.

Affected product: Red Hat OpenStack Platform 16.2. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-4840/ (Markdown: https://insights.sbomify.com/CVE-2024-4840/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4840
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4840
- OSV: https://osv.dev/vulnerability/CVE-2024-4840

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4840/
Summaries are generated and may contain mistakes; the official description above is the record.