Feast through 0.66.0 Authentication Bypass via Unverified Token
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| feast-dev | feast | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Feast-dev | Feast |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.700% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Feast-dev
Feast-dev feast |
|
| Vendors & Products |
Feast-dev
Feast-dev feast |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Feast through 0.66.0 Authentication Bypass via Unverified Token | |
| Weaknesses | CWE-798 | |
| References |
|
|
| Metrics |
cvssV3_1
|