{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-20335 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-20335 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-20335 is a medium-severity vulnerability in MongoDB Ops Manager, published on 11 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-20335 and fix it if it is affected.\n\nWhat it is: CVE-2021-20335 is a medium-severity vulnerability in MongoDB Ops Manager, published on 11 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-20335 in the wild and no public exploit code.\n\nAffected product: MongoDB Ops Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-20335/ (Markdown: https://insights.sbomify.com/CVE-2021-20335/index.md)","id":"CVE-2021-20335","markdown":"https://insights.sbomify.com/CVE-2021-20335/index.md","name":"CVE-2021-20335","record":{"aliases":["GHSA-4hh4-3rxm-gq3h"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"MongoDB Ops Manager","requires_auth":"low_privilege","summary":"An upgrade bug in MongoDB Ops Manager can temporarily disable SSL, exposing data if specific client certificate settings are enabled.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"ops_manager","vendor":"mongodb"}],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"For MongoDB Ops Manager versions prior to and including 4.2.24 with multiple OM application servers, that have SSL turned on for their MongoDB processes, the upgrade to MongoDB Ops Manager versions prior to and including 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SSL may be unexpectedly disabled during upgrade of multiple-server MongoDB Ops Manager","id":"CVE-2021-20335","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Tivoli Netcool/OMNIbus GUI","id":"CVE-2021-20336"},"packages":[],"prev":{"headline":"Local privilege escalation in MongoDB Compass for Windows","id":"CVE-2021-20334"},"products":["MongoDB Ops Manager"],"published":"2021-02-11","related":[{"cvss_score":9.4,"headline":"Ops Manager RCE via webhook body","id":"CVE-2026-8431","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":8.1,"headline":"Potential privilege escalation in Ops Manager API","id":"CVE-2020-7927","kev_date_added":null,"published":"2020-11-23"},{"cvss_score":6.9,"headline":"Ops Manager Uncontrolled Resource Consumption in Monitoring Endpoints","id":"CVE-2026-87110","kev_date_added":null,"published":"2026-10-09"},{"cvss_score":6,"headline":"Ops Manager Sensitive MFA Enrollment Information Exposure in User Listings","id":"CVE-2026-87109","kev_date_added":null,"published":"2026-10-09"},{"cvss_score":5.8,"headline":"Potential exposure of log information in Ops Manager","id":"CVE-2019-2388","kev_date_added":null,"published":"2020-05-13"},{"cvss_score":2.3,"headline":"Ops Manager Improper Authorization in Daily Host Monitoring Retrieval","id":"CVE-2026-87108","kev_date_added":null,"published":"2026-10-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["MongoDB Inc."]},"summary":"An upgrade bug in MongoDB Ops Manager can temporarily disable SSL, exposing data if specific client certificate settings are enabled.","url":"https://insights.sbomify.com/CVE-2021-20335/"}