Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-cwf6-xj49-wp83

HIGH

OpenFeature Operator vulnerable to Cluster-level Privilege Escalation

Also known asCVE-2023-29018GO-2023-1721
Published
Apr 12, 2023
Updated
Aug 20, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk47th percentile-0.06%
0.00%0.41%0.81%1.22%0.2%0.7%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
🐹github.com/open-feature/open-feature-operator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

On a node controlled by an attacker or malicious user, the lax permissions configured on open-feature-operator-controller-manager can be used to further escalate the privileges of any service account in the cluster.

The increased privileges could be used to modify cluster state, leading to DoS, or read sensitive data, including secrets.

Patches

The patch mitigates this issue by restricting the resources the open-feature-operator-controller-manager can modify.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/open-feature/open-feature-operatorall versions0.2.32

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/open-feature/open-feature-operator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/open-feature/open-feature-operator to 0.2.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cwf6-xj49-wp83 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-cwf6-xj49-wp83 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-cwf6-xj49-wp83. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact On a node controlled by an attacker or malicious user, the lax permissions configured on `open-feature-operator-controller-manager` can be used to further escalate the privileges of any service account in the cluster. The increased privileges could be used to modify cluster state, leading to DoS, or read sensitive data, including secrets. ### Patches The patch mitigates this issue by restricting the resources the `open-feature-operator-controller-manager` can modify.
O3 Security · Impact-Aware SCA

Is GHSA-cwf6-xj49-wp83 in your dependencies?

O3 detects GHSA-cwf6-xj49-wp83 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.