First published: Thu Feb 11 2021(Updated: )
For MongoDB Ops Manager <= 4.2.24 with multiple OM application servers, that have SSL turned on for their MongoDB processes, the upgrade to MongoDB Ops Manager <= 4.4.12 triggers a bug where Automation thinks SSL is being turned off, and can disable SSL temporarily for members of the cluster. This issue is temporary and eventually corrects itself after MongoDB Ops Manager instances have finished upgrading to MongoDB Ops Manager 4.4. In addition, customers must be running with clientCertificateMode=OPTIONAL / allowConnectionsWithoutCertificates=true to be impacted*.* Customers upgrading from Ops Manager 4.2.X to 4.2.24 and finally to Ops Manager 4.4.13+ are unaffected by this issue.
Credit: cna@mongodb.com cna@mongodb.com
Affected Software | Affected Version | How to fix |
---|---|---|
MongoDB Ops Manager | >=4.2.0<=4.2.24 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this MongoDB Ops Manager issue is CVE-2021-20335.
The severity of CVE-2021-20335 is medium with a CVSS score of 4.6.
The affected software for CVE-2021-20335 is MongoDB Ops Manager version 4.2.0 to 4.2.24.
The upgrade to MongoDB Ops Manager <= 4.4.12 triggers a bug where Automation thinks SSL is being turned off, and can temporarily disable SSL for members of the cluster.
You can find more information about this vulnerability in the MongoDB Ops Manager release notes: https://docs.opsmanager.mongodb.com/v4.2/release-notes/application/#onprem-server-4-2-23