VoAPI 1.0.0 through 1.2.0 SQL Injection via search Filter Key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| VoAPI | VoAPI | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Voapi | Voapi |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.275% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Voapi
Voapi voapi |
|
| Vendors & Products |
Voapi
Voapi voapi |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | VoAPI 1.0.0 through 1.2.0 contains a sql injection vulnerability that allows authenticated users to inject SQL by supplying crafted column names as search[...] filter keys on list endpoints such as GET /api/log. Attackers can read the HS256 JWT signing secret from the option table and forge a manager role token to take over the /api/m/* management API. | |
| Title | VoAPI 1.0.0 through 1.2.0 SQL Injection via search Filter Key | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV3_1
|