Bi Connector
Monthly
MongoDB BI Connector's mongodrdl tool leaks TLS private-key passwords to standard error when the password is simultaneously supplied via both the connection URI and a corresponding command-line option. Affected versions span BI Connector 2.12.0 through 2.14.29; the fix is version 2.14.30. A local attacker who can read captured stderr output and also possesses the encrypted TLS client key file can combine those two artifacts to authenticate as the legitimate TLS client identity. No public exploit code or active exploitation has been identified at time of analysis.
Unauthenticated remote process termination in MongoDB Connector for BI (mongosqld) affects deployments explicitly configured with Kerberos authentication. An attacker with network access to the mongosqld listener can send a crafted GSSAPI authentication exchange that triggers a double-free condition in error-handling code, crashing the process and interrupting BI availability until restarted. No public exploit code has been identified at time of analysis, and the attack is constrained to the subset of deployments running Kerberos - a non-default configuration.
MongoDB BI Connector's mongodrdl tool leaks TLS private-key passwords to standard error when the password is simultaneously supplied via both the connection URI and a corresponding command-line option. Affected versions span BI Connector 2.12.0 through 2.14.29; the fix is version 2.14.30. A local attacker who can read captured stderr output and also possesses the encrypted TLS client key file can combine those two artifacts to authenticate as the legitimate TLS client identity. No public exploit code or active exploitation has been identified at time of analysis.
Unauthenticated remote process termination in MongoDB Connector for BI (mongosqld) affects deployments explicitly configured with Kerberos authentication. An attacker with network access to the mongosqld listener can send a crafted GSSAPI authentication exchange that triggers a double-free condition in error-handling code, crashing the process and interrupting BI availability until restarted. No public exploit code has been identified at time of analysis, and the attack is constrained to the subset of deployments running Kerberos - a non-default configuration.