nday
CVE-2024-31463 GHSA-g2cm-9v5f-qg7r

Ironic-image allows unauthenticated local access to Ironic API

metal3-io / ironic-image

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

authentication bypass
CWE-288, stated by the CNA GitHub_M and NVD, republishing [email protected]
local
AV:L in CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N (CVSS 3.1) from the CNA GitHub_M
no user interaction
UI:N in CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N (CVSS 3.1) from the CNA GitHub_M
stage
DIS
disclosed
cvss
4.7 MEDIUM v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2024-04-17T15:21Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

Ironic-image is an OpenStack Ironic deployment packaged and configured by Metal3. When the reverse proxy mode is enabled by the IRONIC_REVERSE_PROXY_SETUP variable set to true, 1) HTTP basic credentials are validated on the HTTPD side in a separate container, not in the Ironic service itself and 2) Ironic listens in host network on a private port 6388 on localhost by default. As a result, when the reverse proxy mode is used, any Pod or local Unix user on the control plane Node can access the Ironic API on the private port without authentication. A similar problem affects Ironic Inspector (INSPECTOR_REVERSE_PROXY_SETUP set to true), although the attack potential is smaller there. This issue affects operators deploying ironic-image in the reverse proxy mode, which is the recommended mode when TLS is used (also recommended), with the IRONIC_PRIVATE_PORT variable unset or set to a numeric value. In this case, an attacker with enough privileges to launch a pod on the control plane with host networking can access Ironic API and use it to modify bare-metal machine, e.g. provision them with a new image or change their BIOS settings. This vulnerability is fixed in 24.1.1.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

CVSS 3.1 vector from the CVE record, scored by the CNA GitHub_M.

Event log

+DISdisclosed

CVE record published by GitHub_M. CVSS 4.7, medium.

src cvelist · nday , bulk import · raw
{
  "id": 331223,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2024-31463",
  "occurred_at": "2024-04-17T15:21:49.384Z",
  "observed_at": "2026-11-13T05:38:32.49371Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N",
      "version": "3.1",
      "base_score": 4.7,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2024-07-03T15:16:37.818205Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2024-04-17T15:21:49.384Z",
    "assigner_short_name": "GitHub_M"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.