Some MongoDB Drivers may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when specific authentication-related commands are executed.
Without due care, an application may inadvertently expose this sensitive information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default).
This issue affects the MongoDB C Driver 1.0.0 prior to 1.17.7, MongoDB PHP Driver 1.0.0 prior to 1.9.2, MongoDB Swift Driver 1.0.0 prior to 1.1.1, MongoDB Node.js Driver 3.6 prior to 3.6.10, MongoDB Node.js Driver 4.0 prior to 4.17.0 and MongoDB Node.js Driver 5.0 prior to 5.8.0. This issue also affects users of the MongoDB C++ Driver dependent on the C driver 1.0.0 prior to 1.17.7 (C++ driver prior to 3.7.0).
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| C++ | Mongodb | 1.0.0 (including) | 1.17.7 (excluding) |
| C_driver | Mongodb | 1.0.0 (including) | 1.17.7 (excluding) |
| Node.js | Mongodb | 3.6 (including) | 3.6.10 (excluding) |
| Node.js | Mongodb | 4.0 (including) | 4.17.0 (excluding) |
| Node.js | Mongodb | 5.0 (including) | 5.8.0 (excluding) |
| Php_driver | Mongodb | 1.0.0 (including) | 1.9.2 (excluding) |
| Swift_driver | Mongodb | 1.0.0 (including) | 1.1.1 (excluding) |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: