Feast: feast-operator: feast: default authentication mode is no_auth — shared multi-tenant instances deployed without authentication
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | Red Hat OpenShift AI 2.25 | affected |
|
||||||
| Red Hat | Red Hat OpenShift AI 3.3 | affected |
|
||||||
| Red Hat | Red Hat OpenShift AI 3.4 | affected |
|
||||||
| Red Hat | Red Hat OpenShift AI 3.4 | affected |
|
||||||
| Red Hat | Red Hat OpenShift AI 3.4 | affected |
|
||||||
| Red Hat | Red Hat OpenShift AI 3.4 | affected |
|
||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — | ||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — | ||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — | ||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — | ||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — | ||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — | ||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — | ||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — | ||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — | ||||||
| Red Hat | Red Hat OpenShift AI (RHOAI) | unaffected | — |
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Red Hat | Red Hat Openshift Ai (rhoai) |
|
Vendor Workaround
To mitigate this vulnerability, configure Feast deployments to utilize Kubernetes RBAC authentication. Ensure that `FeatureStore` Custom Resources (CRs) explicitly define an authentication mechanism other than `no_auth`. For Feast SDK usage, avoid the `no_auth` setting in production environments unless `FEAST_INSECURE_NO_AUTH=1` is explicitly set, acknowledging the security implications. Applying these configuration changes will require a redeployment or restart of the affected Feast services.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.904% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:openshift_ai:2.25::el9 cpe:/a:redhat:openshift_ai:3.4::el9 |
|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Red Hat
Red Hat red Hat Openshift Ai (rhoai) |
|
| Vendors & Products |
Red Hat
Red Hat red Hat Openshift Ai (rhoai) |
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:openshift_ai:3.3::el9 | |
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in Feast and feast-operator. The default configuration for both the Feast SDK and the feast-operator is "no_auth," meaning no security manager is installed. This default allows unauthenticated and unauthorized access to feature-server, registry-server, and offline-server endpoints. A remote attacker, by exploiting this missing authentication, could achieve remote code execution (RCE) by storing a malicious User-Defined Function (UDF) on the feature-server, trigger a denial of service (DoS) by forcing re-materialization of all tenant features, and gain unauthorized access to cross-tenant data. | |
| Title | Feast: feast-operator: feast: default authentication mode is no_auth — shared multi-tenant instances deployed without authentication | |
| First Time appeared |
Redhat
Redhat openshift Ai |
|
| Weaknesses | CWE-306 | |
| CPEs | cpe:/a:redhat:openshift_ai | |
| Vendors & Products |
Redhat
Redhat openshift Ai |
|
| References |
| |
| Metrics |
cvssV3_1
|