CVE-2020-35149 json
Code Injection in mquery
published 5y ago modified 4mo ago also GHSA-45q2-34rf-mr94 , EUVD-2020-1478
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
lib/utils.js in mquery before 3.2.3 allows a pollution attack because a special property (e.g., __proto__) can be copied during a merge or clone operation.
Patch / fix
Is CVE-2020-35149 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-35149 updated cvss 4.3
mquery: Code injection via merge or clone operation
-
Red Hat Advanced Cluster Management for Kubernetes 2.1 for RHEL 8 rhacm2/acm-must-gather-rhel8 v2.1.6-6fixed: vendor fix RHSA-2021:1369
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | mquery | <3.2.3 |
3.2.3 |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
github.com
/aheckmann/mquery/commit/792e69fd0a7281a0300be5cade5a6d7c1d468ad4
web, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35149
advisory
Sources
- CVE List CVE-2020-35149
- GitHub Advisory GHSA-45q2-34rf-mr94
- NVD CVE-2020-35149
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.