# CVE-2024-35185: Denial of service of Minder Server with attacker-controlled REST endpoint

> An attacker can crash the Minder server by configuring a malicious REST endpoint that returns excessively large responses, causing memory exhaustion.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 16 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-fjw8-3gp8-4cvx, GO-2024-2864

## What is CVE-2024-35185?

CVE-2024-35185 is a medium-severity denial of service vulnerability in stacklok minder, published on 16 May 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.49, the Minder REST ingester is vulnerable to a denial of service attack via an attacker-controlled REST endpoint that can crash the Minder server. The REST ingester allows users to interact with REST endpoints to fetch data for rule evaluation. When fetching data with the REST ingester, Minder sends a request to an endpoint and will use the data from the body of the response as the data to evaluate against a certain rule. If the response is sufficiently large, it can drain memory on the machine and crash the Minder server. The attacker can control the remote REST endpoints that Minder sends requests to, and they can configure the remote REST endpoints to return responses with large bodies. They would then instruct Minder to send a request to their configured endpoint that would return the large response which would crash the Minder server. Version 0.0.49 fixes this issue.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

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

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


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

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

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

## Is CVE-2024-35185 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35185 is a medium-severity denial of service vulnerability in stacklok minder, published on 16 May 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-35185 in the wild and no public exploit code.

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

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

## Sources

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

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