# CVE-2021-32736: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in think-helper

> Prototype pollution in think-helper allows attackers to modify object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vr5m-3h59-7jcp

## What is CVE-2021-32736?

CVE-2021-32736 is a high-severity vulnerability in thinkjs think-helper, published on 30 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

think-helper defines a set of helper functions for ThinkJS. In versions of think-helper prior to 1.1.3, the software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. The vulnerability is patched in version 1.1.3.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2021-32736?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `think-helper` | npm | All versions | 1.1.3 |
| `think-helper` | npm | All versions | 1.1.3 |

Products: Thinkjs Think-Helper.

## How do I fix CVE-2021-32736?

Upgrade think-helper to 1.1.3 or later.

## Is CVE-2021-32736 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32736 and fix it if it is affected.

What it is: CVE-2021-32736 is a high-severity vulnerability in thinkjs think-helper, published on 30 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32736 in the wild and no public exploit code.

Affected packages and fixed versions:
- think-helper (npm): affected all versions; fixed in 1.1.3
- think-helper (npm): affected all versions; fixed in 1.1.3

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-2021-32736/ (Markdown: https://insights.sbomify.com/CVE-2021-32736/index.md)
```

## Sources

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

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