FastAPI Api Key has a timing side-channel in verify_key that allows statistical key validity detection
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Athroniaeth | fastapi-api-key | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Athroniaeth | Fastapi-api-key | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-95c6-p277-p87g | FastAPI Api Key has a timing side-channel in verify_key that allows statistical key validity detection |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.291% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Athroniaeth fastapi Api Key
|
|
| CPEs | cpe:2.3:a:athroniaeth:fastapi_api_key:*:*:*:*:*:python:*:* | |
| Vendors & Products |
Athroniaeth fastapi Api Key
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Athroniaeth
Athroniaeth fastapi-api-key |
|
| Vendors & Products |
Athroniaeth
Athroniaeth fastapi-api-key |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FastAPI Api Key provides a backend-agnostic library that provides an API key system. Version 1.1.0 has a timing side-channel vulnerability in verify_key(). The method applied a random delay only on verification failures, allowing an attacker to statistically distinguish valid from invalid API keys by measuring response latencies. With enough repeated requests, an adversary could infer whether a key_id corresponds to a valid key, potentially accelerating brute-force or enumeration attacks. All users relying on verify_key() for API key authentication prior to the fix are affected. Users should upgrade to version 1.1.0 to receive a patch. The patch applies a uniform random delay (min_delay to max_delay) to all responses regardless of outcome, eliminating the timing correlation. Some workarounds are available. Add an application-level fixed delay or random jitter to all authentication responses (success and failure) before the fix is applied and/or use rate limiting to reduce the feasibility of statistical timing attacks. | |
| Title | FastAPI Api Key has a timing side-channel in verify_key that allows statistical key validity detection | |
| Weaknesses | CWE-208 | |
| References |
| |
| Metrics |
cvssV3_1
|