MongoDB Connector for BI Improper Error Handling of Log Write Failures May Cause Loss of SQL Service
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in BI Connector 2.14.31.
An unauthenticated party able to reach the port of a MongoDB Connector for BI (mongosqld) instance may generate enough routine connection log activity to exhaust the storage backing the configured log path. When a log write or log rotation operation subsequently fails, the resulting error is not handled and the shared mongosqld process ends, ending service for all connected SQL clients. The process continues to end on startup until an operator restores available storage, and the diagnostic message explaining the condition is not recorded.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| MongoDB | BI Connector | <2.14.31 | 2.14.31 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in MongoDB, strongest first
Embed
A live severity badge for an advisory, README or ticket