Skip to content
Fencer Vulns
medium 6.5

CVE-2024-29156 json

Information leakage in YAQL

published 2024-03-18 2 y ago modified 2026-07-07 4 mo ago also GHSA-mvf6-hwxh-7v76 , PYSEC-2026-2059 , EUVD-2024-0973

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

Summary

In OpenStack Murano through 16.0.0, when YAQL before 3.0.0 is used, the Murano service's MuranoPL extension to the YAQL language fails to sanitize the supplied environment, leading to potential leakage of sensitive service account information.

Patch / fix

  • pypi yaql 3.0.0
  • openstack yaql 3.0.0
  • python-yaql openstack 16.2 1.1.3-9.el8ost
  • python3-yaql openstack 16.2 1.1.3-9.el8ost
  • python3-tripleo-common openstack 16.2 11.7.1-2.20230809225405.e189622.el8ost
  • openstack-tripleo-common openstack 16.2 11.7.1-2.20230809225405.e189622.el8ost
  • openstack-tripleo-heat-templates openstack 16.2 11.6.1-2.20230808225220.el8ost
  • openstack-tripleo-common-devtools openstack 16.2 11.7.1-2.20230809225405.e189622.el8ost
  • openstack-tripleo-common-containers openstack 16.2 11.7.1-2.20230809225405.e189622.el8ost
  • openstack-tripleo-common-container-base openstack 16.2 11.7.1-2.20230809225405.e189622.el8ost

red hat advisories RHSA-2024:4053RHSA-2024:1930RHSA-2024:1931

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-29156 updated cvss 8.4

YAQL: OpenStack Murano Component Information Leakage

  • Red Hat OpenStack Platform 16.1 openstack-heat-api, openstack-heat-common, openstack-heat-engine, openstack-heat-api-cfn, openstack-heat-monolith, openstack-tripleo-heat-templates
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 16.2 openstack-heat-api, openstack-heat-common, openstack-heat-engine, openstack-heat-api-cfn, openstack-heat-monolith
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 17.1 openstack-heat-api, openstack-heat-common, openstack-heat-engine, openstack-heat-api-cfn, openstack-heat-monolith Red Hat OpenStack Platform 18.0 openstack-heat
    affected: no fix available
  • Red Hat OpenStack Platform 16.2 python-yaql 1.1.3-9.el8ost, python3-yaql 1.1.3-9.el8ost, python3-tripleo-common 11.7.1-2.20230809225405.e189622.el8ost, openstack-tripleo-common 11.7.1-2.20230809225405.e189622.el8ost, openstack-tripleo-heat-templates 11.6.1-2.20230808225220.el8ost, openstack-tripleo-common-devtools 11.7.1-2.20230809225405.e189622.el8ost, +2 more
    fixed: vendor fix RHSA-2024:4053
  • Red Hat OpenStack Platform 17.1 python-yaql 1.1.3-11.el8ost, python-yaql 1.1.3-11.el9ost, python3-yaql 1.1.3-11.el8ost, python3-yaql 1.1.3-11.el9ost, openstack-tripleo-heat-templates 14.3.1-17.1.20231103003748.2.el8ost, openstack-tripleo-heat-templates 14.3.1-17.1.20231103010826.2.el9ost
    fixed: vendor fix RHSA-2024:1930

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.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi yaql
<3.0.0
3.0.0

Classification

Weakness
  • CWE-116 Improper Encoding or Escaping of Output
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.