Crafted database metadata may cause memory corruption in MongoDB BI Connector ODBC Driver
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| MongoDB | BI Connector ODBC Driver | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mongodb | Bi Connector Odbc Driver |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.404% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:mongodb:bi_connector_odbc_driver:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mongodb
Mongodb bi Connector Odbc Driver |
|
| Vendors & Products |
Mongodb
Mongodb bi Connector Odbc Driver |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A missing bounds check when parsing stored procedure parameter metadata in the MongoDB BI Connector ODBC Driver can result in an out-of-bounds write in the client application process. Triggering this issue requires control over the server the driver connects to, or the ability to respond in its place, in order to return malformed metadata. The resulting memory corruption may cause the client application to terminate abnormally or, under certain conditions, execute unintended code. | |
| Title | Crafted database metadata may cause memory corruption in MongoDB BI Connector ODBC Driver | |
| Weaknesses | CWE-120 | |
| References |
| |
| Metrics |
cvssV3_1
|