Skip to content

OpenStack Murano Code Execution

Critical severity GitHub Reviewed Published May 17, 2022 to the GitHub Advisory Database • Updated Nov 22, 2023

Package

pip murano (pip)

Affected versions

< 1.0.3

Patched versions

1.0.3
pip murano-dashboard (pip)
< 1.0.3
>= 2.0.0, < 2.0.1
1.0.3
2.0.1
pip python-muranoclient (pip)
< 0.7.3
>= 0.8.0, < 0.8.5
0.7.3
0.8.5

Description

OpenStack Murano before 1.0.3 (liberty) and 2.x before 2.0.1 (mitaka), Murano-dashboard before 1.0.3 (liberty) and 2.x before 2.0.1 (mitaka), and python-muranoclient before 0.7.3 (liberty) and 0.8.x before 0.8.5 (mitaka) improperly use loaders inherited from yaml.Loader when parsing MuranoPL and UI files, which allows remote attackers to create arbitrary Python objects and execute arbitrary code via crafted extended YAML tags in UI definitions in packages.

References

Published by the National Vulnerability Database Sep 26, 2016
Published to the GitHub Advisory Database May 17, 2022
Reviewed Jul 31, 2023
Last updated Nov 22, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

2.704%
(91st percentile)

Weaknesses

CVE ID

CVE-2016-4972

GHSA ID

GHSA-87r7-q54j-f9qg

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.