# CVE-2018-3752: Prototype Pollution in merge-options


- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qw93-45r3-p66p

## What is CVE-2018-3752?

CVE-2018-3752 is a critical vulnerability in n/a, published on 3 Jul 2018. 

### Official description

The utilities function in all versions <= 1.0.0 of the merge-options node module can be tricked into modifying the prototype of Object when the attacker can control part of the structure passed to this function. This can let an attacker add or modify existing properties that will exist on all objects.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-3752?

2 open source packages ship an affected version, including merge-options. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `merge-options` | npm | All versions | 1.0.1 |
| `merge-options` | npm | All versions | 1.0.1 |

Products: Merge-Options Project Merge-Options.

## How do I fix CVE-2018-3752?

Upgrade merge-options to 1.0.1 or later.

## Is CVE-2018-3752 being exploited?

There is no known exploitation of CVE-2018-3752 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3752 and fix it if it is affected.

What it is: CVE-2018-3752 is a critical vulnerability in n/a, published on 3 Jul 2018. 
Exploitation: There is no known exploitation of CVE-2018-3752 in the wild and no public exploit code.

Affected packages and fixed versions:
- merge-options (npm): affected all versions; fixed in 1.0.1
- merge-options (npm): affected all versions; fixed in 1.0.1

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-3752/ (Markdown: https://insights.sbomify.com/CVE-2018-3752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-3752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-3752
- OSV: https://osv.dev/vulnerability/CVE-2018-3752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-3752/
Summaries are generated and may contain mistakes; the official description above is the record.