Skip to content
Fencer Intel
high —

GHSA-m734-r4g6-34f9 json

NoSQL Injection in loopback-connector-mongodb

published 7y ago modified 5y ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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](https://docs.mongodb.com/manual/core/server-side-javascript/) unless disabled ([instructions here](https://docs.mongodb.com/manual/core/server-side-javascript/#disable-server-side-js)).

A proof of concept malicious query:

``` GET /POST filter={"where": {"$where": "function(){sleep(5000); return this.title.contains('Hello');}"}} ```

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.

Patch / fix

  • npm loopback-connector-mongodb 3.6.0

Is GHSA-m734-r4g6-34f9 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm loopback-connector-mongodb
<3.6.0
3.6.0

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.