Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
feast-dev feast
Default version status: unaffected
0 to ≤ 0.66.0affected
pkg:pypi/feastReferences
- https://github.com/feast-dev/feast/issues/6785 ↗
- https://github.com/feast-dev/feast ↗
- https://github.com/feast-dev/feast/blob/v0.66.0/sdk/python/feast/permissions/security_manager.py#L248-L264 ↗
- https://github.com/feast-dev/feast/blob/f296d4b/sdk/python/feast/permissions/auth/oidc_token_parser.py#L152-L156 ↗
- https://github.com/feast-dev/feast/blob/f296d4b/infra/charts/feast-feature-server/templates/deployment.yaml#L46-L47 ↗
- https://www.vulncheck.com/advisories/feast-through-0.66.0-authentication-bypass-via-unverified-token ↗