Patched Fix MongoDB Driver may publish events containing authenticati…

[imhunterand]

…on-related data

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).

const maybeRedact = (commandName, result) => (SENSITIVE_COMMANDS.has(commandName) ? {} : result);
    // NOTE: remove in major revision, this is not spec behavior
    if (SENSITIVE_COMMANDS.has(commandName)) {
      this.commandObj = {};
      this.commandObj[commandName] = true;
    }
    // TODO: NODE-3356 unskip redaction tests
      const testsToSkip =
        loadedSpec.description === 'redacted-commands'
          ? loadedSpec.tests
              .map(test => test.description)
              .filter(
                description =>
                  description !== 'hello without speculative authenticate is not redacted'
              )
          : [];

CVE-2021-32050
CWE-200
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

Problem

What problem are you trying to solve? What issue does this close?

Closes [insert issue #]

Solution

How did you solve the problem?

Deployment Checklist

Any tasks that need to be done on the environment before releasing of this PR (e.g. Setting environment variables, running migrations, etc). If there's no task to be done, put "N/A"

• First task
  • Sub-task 1
  • Sub-task 2
• Second task