# CVE-2024-27916: `GetRepositoryByName`, `DeleteRepositoryByName` and `GetArtifactByName` allow access of arbitrary repositories in Minder by any authenticated user

> Authenticated users can access or delete arbitrary repositories in Minder due to missing authorization checks on specific API endpoints.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-v627-69v2-xx37, GO-2024-2608

## What is CVE-2024-27916?

CVE-2024-27916 is a high-severity missing authorization vulnerability in stacklok minder, published on 6 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Minder is a software supply chain security platform. Prior to version 0.0.33, a Minder user can use the endpoints `GetRepositoryByName`, `DeleteRepositoryByName`, and `GetArtifactByName` to access any repository in the database, irrespective of who owns the repo and any permissions present. The database query checks by repo owner, repo name and provider name (which is always `github`). These query values are not distinct for the particular user - as long as the user has valid credentials and a provider, they can set the repo owner/name to any value they want and the server will return information on this repo. Version 0.0.33 contains a patch for this issue.

Weakness: CWE-285 (Improper Authorization)

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

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 | 0.0.33 |
| `github.com/stacklok/minder` | Go | All versions | 0.0.33 |
| `github.com/stacklok/minder` | Go | All versions | 0.0.33 |

Products: Lfprojects Minder.

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

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

## Is CVE-2024-27916 being exploited?

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

## Other vulnerabilities in stacklok minder

- [CVE-2024-27093](https://insights.sbomify.com/CVE-2024-27093/): Minder trusts client-provided mapping from repo name to upstream ID (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27916 is a high-severity missing authorization vulnerability in stacklok minder, published on 6 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27916 exists.

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

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

## Sources

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

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