Lotus through 0.10.2 Improper Authentication via Event Ingestion API Key Prefix
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| uselotus | lotus | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Uselotus | Lotus |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.362% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Uselotus
Uselotus lotus |
|
| Vendors & Products |
Uselotus
Uselotus lotus |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Lotus through 0.10.2 contains an improper authentication vulnerability in the Go event ingestion middleware that validates API keys by prefix only, without checking the secret against the stored hashed_key. Attackers who know or obtain an API key prefix can submit usage events to POST /api/track/ as that organization, altering its metered usage and billing. | |
| Title | Lotus through 0.10.2 Improper Authentication via Event Ingestion API Key Prefix | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV3_1
|