Skip to content

OpenFeature Operator vulnerable to Cluster-level Privilege Escalation

High severity GitHub Reviewed Published Apr 12, 2023 in open-feature/open-feature-operator • Updated Apr 25, 2023

Package

gomod github.com/open-feature/open-feature-operator (Go)

Affected versions

< 0.2.32

Patched versions

0.2.32

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.

References

@beeme1mr beeme1mr published to open-feature/open-feature-operator Apr 12, 2023
Published to the GitHub Advisory Database Apr 12, 2023
Reviewed Apr 12, 2023
Published by the National Vulnerability Database Apr 14, 2023
Last updated Apr 25, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.156%
(52nd percentile)

Weaknesses

CVE ID

CVE-2023-29018

GHSA ID

GHSA-cwf6-xj49-wp83

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.