MongoDB BI Connector ODBC Driver vulnerabilities

The MongoDB BI Connector ODBC Driver may write outside the bounds of a fixed-size buffer when an application supplies an unusually long catalog, schema, or object name to a metadata retrieval function. This may result in memory corruption within the calling application's process, leading to abnormal termination and, under certain conditions, the potential for arbitrary code execution.

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.

A data source definition with an over-length file path may cause the MongoDB BI Connector ODBC Driver setup dialog to write outside an allocated buffer. The issue stems from incorrect buffer capacity calculation in file/folder selection handling and is triggered only when the user opens the setup dialog and initiates a selection. Depending on build configuration, it may lead to abnormal termination or, under certain conditions, execution of unintended code.

An application using the MongoDB BI Connector ODBC Driver may experience a memory-safety issue when processing output parameters from a stored procedure. Triggering this requires connecting to an untrusted or impersonated database server that returns crafted metadata. This may result in process termination, disclosure of process memory, or, under certain conditions, arbitrary code execution.

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 requires control over the server the driver connects to, or the ability to respond in its place, to return malformed metadata. The resulting memory corruption may cause the client application to terminate abnormally or, under certain conditions, execute unintended code.

The MongoDB BI Connector ODBC Driver converts floating point column values to text without checking if the result fits in the destination buffer. When an application reads a sufficiently large floating point value as text, the driver may write beyond the buffer and corrupt adjacent memory. A user who can store data in a collection read through the BI Connector could crash the application performing the read.