Lotus through 0.10.2 SQL Injection via Subscription Filter Keys
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.449% 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 sql injection vulnerability that allows authenticated organization users to inject SQL by registering crafted subscription_filter_keys that bypass keyword-only validation. Attackers can create subscriptions using the malicious key, which is rendered as an unquoted group-by identifier, to inject SQL into usage aggregation queries against the shared multi-tenant database. | |
| Title | Lotus through 0.10.2 SQL Injection via Subscription Filter Keys | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV3_1
|