Skip to content
Fencer Vulns
medium 5.5

CVE-2024-4840 json

Rhosp-director: cleartext passwords exposed in logs

published 2024-05-13 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-44553

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

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.

Patch / fix

  • Red Hat Red Hat OpenStack Platform 17.1 for RHEL 9 0:14.3.1-17.1.20240919130756.el9ost
  • openstack-tripleo-heat-templates openstack 17.1 14.3.1-17.1.20240919130756.el9ost

red hat advisories RHSA-2024:9978

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-4840 updated cvss 5.5

rhosp-director: cleartext passwords exposed in logs

  • Red Hat OpenStack Platform 16.2 python-tripleoclient
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 17.1 openstack-tripleo-heat-templates 14.3.1-17.1.20240919130756.el9ost
    fixed: vendor fix RHSA-2024:9978

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected products

  • Red Hat Red Hat OpenStack Platform 17.1 for RHEL 9
  • Red Hat Red Hat OpenStack Platform 16.2

Classification

Weakness
  • CWE-312 Cleartext Storage of Sensitive Information

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.