# GHSA-6cj2-92m5-7mvp: Improperly Controlled Modification of Object Prototype Attributes


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Aug 2021

## What is GHSA-6cj2-92m5-7mvp?

GHSA-6cj2-92m5-7mvp is a vulnerability in think-config, published on 3 Aug 2021. 

### Official description

### Impact

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.

### Patches

`think-config@1.1.3` patched it, anyone used `think-config` should upgrade to `>=1.1.3` version.

### References

https://cwe.mitre.org/data/definitions/1321.html

### For more information
If you have any questions or comments about this advisory:
* Open an issue in [thinkjs/thinkjs](https://github.com/thinkjs/thinkjs)
* Email us at [i@imnerd.org](mailto:i@imnerd.org)

## Which versions are affected by GHSA-6cj2-92m5-7mvp?

2 open source packages ship an affected version, including think-config.


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

## How do I fix GHSA-6cj2-92m5-7mvp?

Upgrade think-config to 1.1.3 or later.

## Is GHSA-6cj2-92m5-7mvp being exploited?

There is no known exploitation of GHSA-6cj2-92m5-7mvp in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6cj2-92m5-7mvp and fix it if it is affected.

What it is: GHSA-6cj2-92m5-7mvp is a vulnerability in think-config, published on 3 Aug 2021. 
Exploitation: There is no known exploitation of GHSA-6cj2-92m5-7mvp in the wild and no public exploit code.

Affected packages and fixed versions:
- think-config (npm): affected all versions; fixed in 1.1.3
- think-config (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/GHSA-6cj2-92m5-7mvp/ (Markdown: https://insights.sbomify.com/GHSA-6cj2-92m5-7mvp/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6cj2-92m5-7mvp

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6cj2-92m5-7mvp/
Summaries are generated and may contain mistakes; the official description above is the record.