MongoDB BI Connector ODBC Driver Memory-Safety Issue When Parsing Oversized LIMIT Values
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.366% 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 | An application using the MongoDB BI Connector ODBC Driver may encounter a memory-safety issue when a submitted SQL statement contains an unusually long run of digits following a LIMIT clause. The issue occurs only on connections where the driver's optional prefetch setting is enabled, and stems from the driver copying the digit sequence into a fixed-size internal buffer without checking its length. A user able to influence the numeric portion of a LIMIT clause could cause the hosting application process to terminate unexpectedly or corrupt adjacent memory in that process. | |
| Title | MongoDB BI Connector ODBC Driver Memory-Safety Issue When Parsing Oversized LIMIT Values | |
| Weaknesses | CWE-121 | |
| References |
| |
| Metrics |
cvssV3_1
|