# GHSA-84p7-fh9c-6g8h: Prototype Pollution in mixme

> Prototype pollution in mixme allows attackers to modify object properties, potentially leading to security bypasses or data manipulation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Sep 2021

## What is GHSA-84p7-fh9c-6g8h?

GHSA-84p7-fh9c-6g8h is a vulnerability in mixme, published on 20 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact
When copying properties from a source object to a target object, the target object can gain access to certain properties of the source object and modify their content.

### Patches
The problem was patch with a more agressive discovery of secured properties to filter out.

## Which versions are affected by GHSA-84p7-fh9c-6g8h?

2 open source packages ship an affected version, including mixme.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mixme` | npm | All versions | 0.5.2 |
| `mixme` | npm | All versions | 0.5.2 |

## How do I fix GHSA-84p7-fh9c-6g8h?

Upgrade mixme to 0.5.2 or later.

## Is GHSA-84p7-fh9c-6g8h being exploited?

There is no known exploitation of GHSA-84p7-fh9c-6g8h in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-84p7-fh9c-6g8h and fix it if it is affected.

What it is: GHSA-84p7-fh9c-6g8h is a vulnerability in mixme, published on 20 Sep 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 GHSA-84p7-fh9c-6g8h in the wild and no public exploit code.

Affected packages and fixed versions:
- mixme (npm): affected all versions; fixed in 0.5.2
- mixme (npm): affected all versions; fixed in 0.5.2

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-84p7-fh9c-6g8h/ (Markdown: https://insights.sbomify.com/GHSA-84p7-fh9c-6g8h/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-84p7-fh9c-6g8h

---
From sbomify Insights: https://insights.sbomify.com/GHSA-84p7-fh9c-6g8h/
Summaries are generated and may contain mistakes; the official description above is the record.