REDHAT-BUG-2484318: High severity MLflow MLflow vulnerability
A vulnerability in mlflow/mlflow versions prior to 3.11.0 allows for the resolution of environment variables in AI Gateway secrets, which can be exploited to exfiltrate sensitive server-side environment credentials to an attacker-controlled endpoint. This issue arises because the apikey field in gateway secrets can accept $ENVVAR references, which are resolved against the MLflow server's environment during runtime. The resolved secrets are then sent in provider authentication headers to the configured upstream apibase. This vulnerability can be exploited by low-privileged authenticated users in basic-auth deployments or by unauthenticated users in default deployments without basic-auth. The impact includes potential leakage of sensitive credentials such as cloud artifact credentials (AWSACCESSKEYID, AWSSECRETACCESSKEY), which could lead to artifact poisoning and cross-boundary code execution in downstream environments. The issue is fixed in version 3.11.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
mlflow/mlflowto a version that resolves this vulnerability.Fixed in 3.11.0
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2484318?
The severity of REDHAT-BUG-2484318 is rated as high with a score of 7.
How do I fix REDHAT-BUG-2484318?
To fix REDHAT-BUG-2484318, upgrade to MLflow version 3.11.0 or later.
What does REDHAT-BUG-2484318 exploit?
REDHAT-BUG-2484318 exploits the resolution of environment variables in AI Gateway secrets to exfiltrate sensitive credentials.
What versions are affected by REDHAT-BUG-2484318?
MLflow versions prior to 3.11.0 are affected by REDHAT-BUG-2484318.
What type of credentials are at risk in REDHAT-BUG-2484318?
The credentials at risk in REDHAT-BUG-2484318 are sensitive server-side environment credentials.