Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-72839

Server skips peer certificate validation if neither CAFile nor clusterCAFile is provided

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc4, 7.0.6, 5.0.25, 4.4.29, 6.0.14
    • 7.0.5, 6.0.13, 5.0.24, 4.4.28
    • None
    • None
    • Server Security
    • Fully Compatible
    • ALL
    • v7.0, v6.0, v5.0, v4.4, v4.2
    • Security 2023-01-23, Security 2023-02-06, Security 2023-02-20, Security 2023-03-06, Security 2023-03-20, Security 2023-04-03, Security 2023-04-17, Security 2023-05-01, Security 2023-05-15, Security 2023-05-29, Security 2023-06-12, Security 2023-06-26, Security 2023-07-10, Security 2023-07-24, Security 2023-08-07, Security 2023-08-21, Security 2023-09-04, Security 2023-09-18

    Description

      The documentation says that:

      If --tlsCAFile or tls.CAFile is not specified and you are not using x.509 authentication, the system-wide CA certificate store will be used when connecting to an TLS-enabled server.

      However, when a server is configured with neither CAFile nor clusterCAFile, it will skip peer certificate validation on both ingress and egress TLS connections. The expectation is that on egress connection, the node (client) should at least verify the peer (server's) certificate using the system CA cert store.

      Note, this only applies to server processes (mongod and mongos), the shell is not affected.

      Attachments

        Activity

          People

            brad.moore@mongodb.com Brad Moore
            erwin.pe@mongodb.com Erwin Pe
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: