# CVE-2024-33398: piraeus-operator allows attacker to impersonate service account

> An attacker can impersonate a service account to list cluster secrets due to excessive ClusterRole permissions in the piraeus-operator.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6fg2-hvj9-832f, GO-2024-2811, MINI-628p-pq29-gfr2, MINI-f534-wvmq-3vcw

## What is CVE-2024-33398?

CVE-2024-33398 is a high-severity vulnerability in n/a, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a ClusterRole in piraeus-operator v2.5.0 and earlier which has been granted list secrets permission, which allows an attacker to impersonate the service account bound to this ClusterRole and use its high-risk privileges to list confidential information across the cluster.

Weakness: CWE-269 (Improper Privilege Management)

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

4 open source packages ship an affected version, including github.com/piraeusdatastore/piraeus-operator/v2 and github.com/piraeusdatastore/piraeus-operator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/piraeusdatastore/piraeus-operator/v2` | Go | All versions | None |
| `github.com/piraeusdatastore/piraeus-operator/v2` | Go | All versions to 2.5.0 | None |
| `github.com/piraeusdatastore/piraeus-operator/v2` | Go | All versions to 2.5.0 | None |
| `github.com/piraeusdatastore/piraeus-operator` | Go | All versions | None |

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

Upgrade to a fixed version.

## Is CVE-2024-33398 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33398 is a high-severity vulnerability in n/a, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33398 exists.

Affected packages and fixed versions:
- github.com/piraeusdatastore/piraeus-operator/v2 (Go): affected all versions; no fix listed
- github.com/piraeusdatastore/piraeus-operator/v2 (Go): affected all versions up to 2.5.0; no fix listed
- github.com/piraeusdatastore/piraeus-operator/v2 (Go): affected all versions up to 2.5.0; no fix listed
- github.com/piraeusdatastore/piraeus-operator (Go): affected all versions; no fix listed

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

## Sources

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

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