Skip to content

← Public intelligence

npm package

loopback-connector-mongodb

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

    NoSQL Injection in loopback-connector-mongodb

    GHSA-hxwc-5vw9-2w4w

    Affected
    • npm loopback-connector-mongodb <= 3.5.0
    Fixed in
    3.6.0· Vendor fix available
    Issue
    Versions of loopback-connector-mongodb prior to 3.6.0 are vulnerable to NoSQL Injection. Filters passed to the database query are not properly sanitized which leads to execution of code on the database driver and data leak. Recommendation Upgrade to version 3.6.0 or later.

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

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. UnratednpmAmendedPublished

    NoSQL Injection in loopback-connector-mongodb

    GHSA-m734-r4g6-34f9

    Affected
    • npm loopback-connector-mongodb < 3.6.0
    Fixed in
    3.6.0· Vendor fix available
    Issue
    Versions of loopback-connector-mongodb before 3.6.0 are vulnerable to NoSQL injection. MongoDB Connector for LoopBack fails to properly sanitize a filter passed to query the database by allowing the dangerous $where property to be passed to the MongoDB Driver. The Driver allows the special $where property in a filter to execute JavaScript (client can pass in a malicious script) on the database Driver. This is an intended feature of MongoDB unless disabled (instructions here). A proof of concept malicious query: The above makes the database sleep for 5 seconds and then returns all “Posts” with the title containing the word Hello. Recommendation Update to version 3.6.0 or later.

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

    Sources:osv.dev (1)github.com (2)Source checked Evidence →