# openSUSE-SU-2024:0095-1: Security update for kanidm

> An administrator can trigger a thread crash in Kanidm's OAuth2 claim maps, causing a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2024

## What is openSUSE-SU-2024:0095-1?

openSUSE-SU-2024:0095-1 is a denial of service vulnerability in kanidm, published on 30 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

This update for kanidm fixes the following issues:

Update to version 1.1.0~rc16~git6.e51d0de:

* [SECURITY: LOW] Administrator triggered thread crash in oauth2 claim maps #2686 (#2686)
* return consent map to service account (#2604)

## Which versions are affected by openSUSE-SU-2024:0095-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kanidm` | SUSE:Package Hub 15 SP5 | All versions | 1.1.0~rc16~git6.e51d0de-bp155.14.1 |
| `kanidm` | openSUSE:Leap 15.5 | All versions | 1.1.0~rc16~git6.e51d0de-bp155.14.1 |

## How do I fix openSUSE-SU-2024:0095-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2024:0095-1 being exploited?

There is no known exploitation of openSUSE-SU-2024:0095-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2024:0095-1 and fix it if it is affected.

What it is: openSUSE-SU-2024:0095-1 is a denial of service vulnerability in kanidm, published on 30 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2024:0095-1 in the wild and no public exploit code.

Affected product: kanidm. 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/openSUSE-SU-2024-0095-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2024-0095-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2024:0095-1

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