# CVE-2024-54450: Security feature bypass in n/a

> Attackers can spoof IP addresses via X-Forwarded-For headers, bypassing IP-based security controls and misleading audit logs in Kurmi Provisioning Suite.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2024
- **Updated:** 28 Dec 2024
- **Also known as:** GHSA-9rf3-44g3-h94q

## What is CVE-2024-54450?

CVE-2024-54450 is a critical vulnerability in n/a, published on 27 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Kurmi Provisioning Suite 7.9.0.33. If an X-Forwarded-For header is received during authentication, the Kurmi application will record the (possibly forged) IP address mentioned in that header rather than the real IP address that the user logged in from. This fake IP address can later be displayed in the My Account popup that shows the IP address that was used to log in.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2024-54450 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54450 is a critical vulnerability in n/a, published on 27 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-54450 in the wild and no public exploit code.

Affected product: n/a. 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-54450/ (Markdown: https://insights.sbomify.com/CVE-2024-54450/index.md)
```

## Sources

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

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