Skip to content

Unauthenticated access to Ironic API

High
tuminoid published GHSA-jwpr-9fwh-m4g7 Aug 25, 2023

Package

ironic-image (Docker image)

Affected versions

< capm3-v1.4.3

Patched versions

capm3-v1.4.3

Description

Impact

Ironic-image is a container image to run OpenStack Ironic as part of Metal³. If Ironic is not deployed with TLS and it does not have API and Conductor split into separate services, access to the API is not protected by any authentication. Ironic API is also listening in host network. In case the node is not behind a firewall, the API could be accessed by anyone via network without authentication.

By default, Ironic API in Metal3 is protected by TLS and basic authentication, so this vulnerability requires operator to configure API without TLS for it to be vulnerable. TLS and authentication however should not be coupled as they are in versions prior capm3-v1.4.3.

Patches

Issue exists in all versions before image tag capm3-v1.4.3. Upgrade ironic-image to tag capm3-v1.4.3 or newer.

Workarounds

  1. Configure TLS for Ironic API (deploy.sh -t ..., IRONIC_TLS_SETUP=true)
  2. Split Ironic API and Conductor via configuration change (old implementation, not recommended)

With both workarounds, services are configured with httpd front-end, which has proper authentication configuration in place.

References

  1. f64bb6c
  2. https://nvd.nist.gov/vuln/detail/CVE-2023-40585

Severity

High

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
Low
Integrity
Low
Availability
Low

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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

CVE ID

CVE-2023-40585

Weaknesses