# CVE-2024-31463: Ironic-image allows unauthenticated local access to Ironic API

> Attackers with local pod access can bypass authentication to modify bare-metal machines when reverse proxy mode is enabled.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-g2cm-9v5f-qg7r

## What is CVE-2024-31463?

CVE-2024-31463 is a medium-severity authentication bypass vulnerability in metal3-io ironic-image, published on 17 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2024-31463?


## How do I fix CVE-2024-31463?

No fix has been published for CVE-2024-31463 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-31463 being exploited?

There is no known exploitation of CVE-2024-31463 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31463 and fix it if it is affected.

What it is: CVE-2024-31463 is a medium-severity authentication bypass vulnerability in metal3-io ironic-image, published on 17 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31463 in the wild and no public exploit code.

Affected product: metal3-io ironic-image. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-31463/ (Markdown: https://insights.sbomify.com/CVE-2024-31463/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-31463
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-31463
- OSV: https://osv.dev/vulnerability/CVE-2024-31463

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-31463/
Summaries are generated and may contain mistakes; the official description above is the record.