# CVE-2024-5250: Overly Verbose Errors in SAML Integration

> Attackers can obtain sensitive information from overly verbose error messages in SAML integrations, potentially aiding further attacks.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **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:** 30 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-mjjp-275q-ww9c

## What is CVE-2024-5250?

CVE-2024-5250 is a low-severity vulnerability in Akana API Platform, published on 30 Jul 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 versions of Akana API Platform prior to 2024.1.0 overly verbose errors can be found in SAML integrations

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

It affects 1 product.


Products: Perforce Akana Api.

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

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

## Is CVE-2024-5250 being exploited?

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

## Other vulnerabilities in Akana API Platform

- [CVE-2024-3930](https://insights.sbomify.com/CVE-2024-3930/): XML External Entity in Akana (medium 6.3)
- [CVE-2024-5249](https://insights.sbomify.com/CVE-2024-5249/): SAML Replay in Akana (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5250 is a low-severity vulnerability in Akana API Platform, published on 30 Jul 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-5250 in the wild and no public exploit code.

Affected product: Akana API Platform. 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-5250/ (Markdown: https://insights.sbomify.com/CVE-2024-5250/index.md)
```

## Sources

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

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