CVE-2024-11602 Overview
CVE-2024-11602 is a Cross-Origin Resource Sharing (CORS) misconfiguration in feast-dev/feast version 0.40.0. The CORS policy on the agentscope server fails to restrict access to trusted origins. Any external domain can send authenticated requests to the API. Attackers can abuse this weakness to bypass same-origin protections and read sensitive data from the server. The issue maps to CWE-346: Origin Validation Error and requires user interaction, typically by luring a victim to a malicious page that issues cross-origin requests to the vulnerable endpoint.
Critical Impact
A permissive CORS policy allows attacker-controlled origins to read authenticated API responses from the Feast agentscope server, exposing sensitive feature store data.
Affected Products
- feast-dev/feast version 0.40.0
- Feast agentscope server component
- Deployments exposing the Feast API to browser-based clients
Discovery Timeline
- 2025-03-20 - CVE-2024-11602 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-11602
Vulnerability Analysis
The vulnerability resides in the CORS configuration of the Feast agentscope server. The server responds to preflight and simple cross-origin requests with headers that reflect or wildcard arbitrary origins. When a browser sends a request from an attacker-controlled site, the server responds with Access-Control-Allow-Origin values that permit the response to be read by that origin. If credentials or session state are involved, sensitive feature data can be exfiltrated to the attacker.
The flaw is exploitable over the network without authentication on the attacker side, but requires the victim to interact with a malicious page. The scope changes because a browser security boundary is crossed, and confidentiality of API data is directly impacted.
Root Cause
The root cause is improper origin validation [CWE-346]. The CORS middleware does not enforce an allowlist of trusted origins. Instead, it accepts any Origin header value, undermining the same-origin policy that browsers enforce by default.
Attack Vector
An attacker hosts a malicious page that issues fetch or XMLHttpRequest calls to the vulnerable Feast agentscope endpoint. A logged-in user visiting the page triggers the request from their browser. The server returns permissive CORS headers, allowing the attacker's JavaScript to read the response body and forward it to an attacker-controlled server. Refer to the Huntr Bug Bounty Report for the reproduction steps and affected endpoints.
Detection Methods for CVE-2024-11602
Indicators of Compromise
- HTTP responses from the Feast agentscope server containing Access-Control-Allow-Origin: * or reflected arbitrary origins alongside Access-Control-Allow-Credentials: true.
- Unexpected cross-origin OPTIONS preflight requests to Feast API endpoints from unknown referrers.
- Outbound browser traffic from user workstations to unfamiliar domains immediately after accessing Feast dashboards.
Detection Strategies
- Audit HTTP response headers from the Feast agentscope server for wildcard or reflected Access-Control-Allow-Origin values.
- Instrument web proxies to flag CORS responses that reflect the request Origin header verbatim on sensitive API paths.
- Review web server access logs for OPTIONS requests with Origin headers that do not match approved application domains.
Monitoring Recommendations
- Continuously monitor Feast API traffic for anomalous Origin header values and unexpected cross-origin patterns.
- Alert on browser telemetry showing script-initiated requests to /get-online-features or similar Feast endpoints from non-approved pages.
- Track user session activity for concurrent requests originating from unfamiliar referrers.
How to Mitigate CVE-2024-11602
Immediate Actions Required
- Restrict the Feast agentscope server to an explicit allowlist of trusted origins in the CORS configuration.
- Remove wildcard Access-Control-Allow-Origin: * values, especially when responses include credentials or session cookies.
- Place the agentscope server behind an authenticated reverse proxy that enforces strict origin validation.
- Upgrade to a Feast release later than 0.40.0 that addresses the CORS configuration, once available from the maintainers.
Patch Information
No vendor patch reference is listed in the enriched CVE data. Monitor the feast-dev/feast repository and the Huntr Bug Bounty Report for remediation guidance and version updates.
Workarounds
- Configure the CORS middleware to reject any Origin header not present in a hardcoded allowlist of internal domains.
- Disable Access-Control-Allow-Credentials for endpoints that do not require authenticated cross-origin access.
- Enforce SameSite=Strict on session cookies used by Feast clients to reduce cross-origin credential leakage.
- Segment the Feast agentscope server on an internal network and block direct browser access from untrusted networks.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
