{"answers":{"affected":"2 open source packages ship an affected version, including loopback-connector-mongodb.","exploited":"There is no known exploitation of GHSA-m734-r4g6-34f9 in the wild and no public exploit code.","fix":"Upgrade loopback-connector-mongodb to 3.6.0 or later.","what":"GHSA-m734-r4g6-34f9 is a code injection vulnerability in loopback-connector-mongodb, published on 4 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-m734-r4g6-34f9 and fix it if it is affected.\n\nWhat it is: GHSA-m734-r4g6-34f9 is a code injection vulnerability in loopback-connector-mongodb, published on 4 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-m734-r4g6-34f9 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- loopback-connector-mongodb (npm): affected all versions; fixed in 3.6.0\n- loopback-connector-mongodb (npm): affected all versions; fixed in 3.6.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-m734-r4g6-34f9/ (Markdown: https://insights.sbomify.com/GHSA-m734-r4g6-34f9/index.md)","id":"GHSA-m734-r4g6-34f9","markdown":"https://insights.sbomify.com/GHSA-m734-r4g6-34f9/index.md","name":"GHSA-m734-r4g6-34f9","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"LoopBack MongoDB connector","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript on the database via NoSQL injection in the LoopBack MongoDB connector, leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Versions of `loopback-connector-mongodb` before 3.6.0 are vulnerable to NoSQL injection.\n\nMongoDB 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)).\n\nA proof of concept malicious query:\n\n```\nGET /POST filter={\"where\": {\"$where\": \"function(){sleep(5000); return this.title.contains('Hello');}\"}}\n```\n\nThe above makes the database sleep for 5 seconds and then returns all “Posts” with the title containing the word `Hello`.\n\n## Recommendation\n\nUpdate to version 3.6.0 or later.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"NoSQL Injection in loopback-connector-mongodb","id":"GHSA-m734-r4g6-34f9","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["3.6.0"],"introduced":["0"],"last_affected":[],"package":"loopback-connector-mongodb","purl":null,"source":"GHSA-m734-r4g6-34f9"},{"ecosystem":"npm","fixed":["3.6.0"],"introduced":["0"],"last_affected":[],"package":"loopback-connector-mongodb","purl":"pkg:npm/loopback-connector-mongodb","source":"GHSA-m734-r4g6-34f9"}],"products":null,"published":"2019-06-04","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can execute arbitrary JavaScript on the database via NoSQL injection in the LoopBack MongoDB connector, leading to code execution or denial of service.","url":"https://insights.sbomify.com/GHSA-m734-r4g6-34f9/"}