# CVE-2024-27093: Minder trusts client-provided mapping from repo name to upstream ID

> Attackers can bypass security remediation by registering repositories with mismatched upstream IDs, preventing policy enforcement and causing denial of service.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L`)
- **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:** Yes
- **Published:** 26 Feb 2024
- **Updated:** 27 Aug 2024
- **Also known as:** GHSA-q6h8-4j2v-pjg4, GO-2024-2582

## What is CVE-2024-27093?

CVE-2024-27093 is a medium-severity vulnerability in stacklok minder, published on 26 Feb 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

Minder is a Software Supply Chain Security Platform. In version 0.0.31 and earlier, it is possible for an attacker to register a repository with a invalid or differing upstream ID, which causes Minder to report the repository as registered, but not remediate any future changes which conflict with policy (because the webhooks for the repo do not match any known repository in the database).  When attempting to register a repo with a different repo ID, the registered provider must have admin on the named repo, or a 404 error will result.  Similarly, if the stored provider token does not have repo access, then the remediations will not apply successfully.  Lastly, it appears that reconciliation actions do not execute against repos with this type of mismatch. This appears to primarily be a potential denial-of-service vulnerability.  This vulnerability is patched in version 0.20240226.1425+ref.53868a8.

Weakness: CWE-20 (Improper Input Validation)

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

3 open source packages ship an affected version, including github.com/stacklok/minder. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/stacklok/minder` | Go | All versions | None |
| `github.com/stacklok/minder` | Go | All versions | 0.20240226.1425 |
| `github.com/stacklok/minder` | Go | All versions | 0.20240226.1425 |

Products: Lfprojects Minder.

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

Upgrade github.com/stacklok/minder to 0.20240226.1425 or later.

## Is CVE-2024-27093 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27093 exists.

## Other vulnerabilities in stacklok minder

- [CVE-2024-27916](https://insights.sbomify.com/CVE-2024-27916/): `GetRepositoryByName`, `DeleteRepositoryByName` and `GetArtifactByName` allow access of arbitrary repositories in Minder by any authenticated user (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27093 is a medium-severity vulnerability in stacklok minder, published on 26 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27093 exists.

Affected packages and fixed versions:
- github.com/stacklok/minder (Go): affected all versions; no fix listed
- github.com/stacklok/minder (Go): affected all versions; fixed in 0.20240226.1425
- github.com/stacklok/minder (Go): affected all versions; fixed in 0.20240226.1425

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-27093/ (Markdown: https://insights.sbomify.com/CVE-2024-27093/index.md)
```

## Sources

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

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