# CVE-2023-29018: OpenFeature Operator vulnerable to Cluster-level Privilege Escalation

> An attacker with code execution can escalate privileges via lax operator permissions to modify cluster state or read secrets.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Apr 2023
- **Updated:** 6 Feb 2025
- **Also known as:** GHSA-cwf6-xj49-wp83, GO-2023-1721

## What is CVE-2023-29018?

CVE-2023-29018 is a high-severity vulnerability in open-feature-operator, published on 14 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The OpenFeature Operator allows users to expose feature flags to applications. Assuming the pre-existence of a vulnerability that allows for arbitrary code execution, an attacker could leverage the lax permissions configured on `open-feature-operator-controller-manager` to escalate the privileges of any SA in the cluster. The increased privileges could be used to modify cluster state, leading to DoS, or read sensitive data, including secrets. Version 0.2.32 mitigates this issue by restricting the resources the `open-feature-operator-controller-manager` can modify.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2023-29018?

3 open source packages ship an affected version, including github.com/open-feature/open-feature-operator. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/open-feature/open-feature-operator` | Go | All versions | 0.2.32 |
| `github.com/open-feature/open-feature-operator` | Go | All versions | 0.2.32 |
| `github.com/open-feature/open-feature-operator` | Go | All versions | 0.2.32 |

Products: Linuxfoundation Openfeature.

## How do I fix CVE-2023-29018?

Upgrade github.com/open-feature/open-feature-operator to 0.2.32 or later.

## Is CVE-2023-29018 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29018 and fix it if it is affected.

What it is: CVE-2023-29018 is a high-severity vulnerability in open-feature-operator, published on 14 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-29018 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/open-feature/open-feature-operator (Go): affected all versions; fixed in 0.2.32
- github.com/open-feature/open-feature-operator (Go): affected all versions; fixed in 0.2.32
- github.com/open-feature/open-feature-operator (Go): affected all versions; fixed in 0.2.32

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

## Sources

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

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