Summary
NoSQL Injection in loopback-connector-mongodb
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:
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.
Impact
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Update to version 3.6.0 or later.
Frequently Asked Questions
- What is GHSA-M734-R4G6-34F9? GHSA-M734-R4G6-34F9 is a high-severity SQL injection vulnerability in loopback-connector-mongodb (npm), affecting versions < 3.6.0. It is fixed in 3.6.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of loopback-connector-mongodb are affected by GHSA-M734-R4G6-34F9? loopback-connector-mongodb (npm) versions < 3.6.0 is affected.
- Is there a fix for GHSA-M734-R4G6-34F9? Yes. GHSA-M734-R4G6-34F9 is fixed in 3.6.0. Upgrade to this version or later.
- Is GHSA-M734-R4G6-34F9 exploitable, and should I be worried? Whether GHSA-M734-R4G6-34F9 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-M734-R4G6-34F9 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-M734-R4G6-34F9? Upgrade
loopback-connector-mongodbto 3.6.0 or later.