# CVE-2024-2005: SAML implementation allows privilege escalation

> A misconfiguration in the SAML implementation allows attackers to escalate privileges in Blue Planet products using SAML authentication.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Mar 2024
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-j7p2-m4ff-pw4r

## What is CVE-2024-2005?

CVE-2024-2005 is a critical vulnerability in Blue Planet Inventory (BPI), published on 5 Mar 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In Blue Planet®  products through 22.12, a misconfiguration in the SAML implementation allows for privilege escalation. Only products using SAML authentication are affected.

Blue Planet® has released software updates that address this vulnerability for the affected products. Customers are advised to upgrade their Blue Planet products to the latest software version as soon as possible. The software updates can be downloaded from the Ciena Support Portal.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Ciena Blue Planet Inventory.

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

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

## Is CVE-2024-2005 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2005 is a critical vulnerability in Blue Planet Inventory (BPI), published on 5 Mar 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-2005 in the wild and no public exploit code.

Affected product: Blue Planet Inventory (BPI). 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-2005/ (Markdown: https://insights.sbomify.com/CVE-2024-2005/index.md)
```

## Sources

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

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