Skip to content

← Public intelligence

NuGet package

mongodb.driver

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.2NuGetPublished

    MongoDB .NET/C# Driver vulnerable to Deserialization of Untrusted Data

    CVE-2022-48282 · GHSA-7j9m-j397-g4wx

    Affected
    • NuGet mongodb.driver < 2.19.0
    Fixed in
    2.19.0· Vendor fix available
    Issue
    Under very specific circumstances, a privileged user is able to cause arbitrary code to be executed which may cause further disruption to services. This is specific to applications written in C#. This affects all MongoDB .NET/C Driver versions prior to and including v2.18.0

    Recommended action: Upgrade to 2.19.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 4.9NuGetPublished

    MongoDB C# Driver Risk of Exposing Authentication Data via Command Listener

    CVE-2021-20331 · GHSA-p9rv-qgqw-jx2w

    Affected
    • NuGet mongodb.driver >= 2.11.0, < 2.12.2
    Fixed in
    2.12.2· Vendor fix available
    Issue
    Specific versions of the MongoDB C Driver 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 commands such as "saslStart", "saslContinue", "isMaster", "createUser", and "updateUser" are executed. Without due care, an application may inadvertently expose this authenticated-related 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 2.12 <= 2.12.1.

    Recommended action: Upgrade to 2.12.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →