# CVE-2024-31455: Minder GetRepositoryByName data leak

> Attackers can retrieve random repository data due to a missing parenthesis in a SQL query, exposing sensitive information.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-ggp5-28x4-xcj9, GO-2024-2701

## What is CVE-2024-31455?

CVE-2024-31455 is a medium-severity vulnerability in stacklok minder, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Minder by Stacklok is an open source software supply chain security platform. A refactoring in commit `5c381cf` added the ability to get GitHub repositories registered to a project without specifying a specific provider.  Unfortunately, the SQL query for doing so was missing parenthesis, and would select a random repository. This issue is patched in pull request 2941. As a workaround, revert prior to `5c381cf`, or roll forward past `2eb94e7`.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/stacklok/minder` | Go | From 0.0.39 | 0.0.40 |
| `github.com/stacklok/minder` | Go | From 0.0.39 | 0.0.40 |
| `github.com/stacklok/minder` | Go | From 0.0.39 | 0.0.40 |

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

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

## Is CVE-2024-31455 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31455 is a medium-severity vulnerability in stacklok minder, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31455 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/stacklok/minder (Go): affected from 0.0.39; fixed in 0.0.40
- github.com/stacklok/minder (Go): affected from 0.0.39; fixed in 0.0.40
- github.com/stacklok/minder (Go): affected from 0.0.39; fixed in 0.0.40

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

## Sources

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

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