DataRoom through 3.0.0 SQL Injection via MyBatisService.generateSql
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| gcpaas | DataRoom | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Gcpaas | Dataroom |
|
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)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gcpaas
Gcpaas dataroom |
|
| Vendors & Products |
Gcpaas
Gcpaas dataroom |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | DataRoom through 3.0.0 contains an sql injection vulnerability in MyBatisService.generateSql that allows sharer-role users to inject SQL by supplying crafted dataset parameters. Attackers can send crafted inputParam values to /dataRoom/dataset/run, exploiting unquoted string parameters or MySQL backslash escapes, to execute injected SQL against the database. | |
| Title | DataRoom through 3.0.0 SQL Injection via MyBatisService.generateSql | |
| Weaknesses | CWE-89 | |
| References |
|
|
| Metrics |
cvssV3_1
|