Feast through 0.66.0 fails to verify JWT token signatures before establishing user identity, allowing attackers to bypass all role-based access control by presenting an unverified token with a hardcoded claim value. Attackers can obtain trusted internal identity and gain unchecked read and write access to all entities, feature views, data sources, and permission policies on the server.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
High
Complete denial of service
CVSS Vector v4.0
Weakness Type (CWE)
References 6
https://github.com/feast-dev/feast
disclosure@vulncheck.com
https://github.com/feast-dev/feast/blob/f296d4b/infra/charts/feast-feature-serv…
disclosure@vulncheck.com
https://github.com/feast-dev/feast/blob/f296d4b/sdk/python/feast/permissions/au…
disclosure@vulncheck.com
https://github.com/feast-dev/feast/blob/v0.66.0/sdk/python/feast/permissions/se…
disclosure@vulncheck.com
https://github.com/feast-dev/feast/issues/6785
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/feast-through-0.66.0-authentication-bypass…
disclosure@vulncheck.com