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

OCSP validation should consider errors caused by shutdown to be fatal

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Server Security

      When the OCSP subsystem attempts to reach out to a remote system, it might find that the MongoDB Server which it is running within is shutting down. It should never be possible for this error to be confused with a network fault and result in "soft failure". Instead, OCSPManager::requestStatus should explicitly propagate ErrorCodes::ShutdownInProgress to its caller. dispatchOCSPRequests should consider this error to be a "strong" error, and propagate it up. The OCSPCache should permit the error to propagate up to SSLManagerOpenSSL::ocspClientVerification which should consider the result to indicate that it should reject the certificate it is validating.

            Assignee:
            backlog-server-security [DO NOT USE] Backlog - Security Team
            Reporter:
            spencer.jackson@mongodb.com Spencer Jackson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: