CyberRota Analysis
AI-GeneratedThe Feast SDK and feast-operator are vulnerable due to their default "no_auth" configuration, which permits unauthenticated access to critical endpoints. This flaw could allow remote attackers to execute arbitrary code, cause denial of service by re-materializing tenant features, and access sensitive cross-tenant data. Organizations using Feast should prioritize this vulnerability to mitigate potential exploitation risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.