# CVE-2024-39018: @cat5th/key-serializer Prototype Pollution vulnerability

> Attackers can execute arbitrary code or cause denial of service via prototype pollution in the key-serializer library.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-whpx-g542-7c7v

## What is CVE-2024-39018?

CVE-2024-39018 is a medium-severity code injection vulnerability in n/a, published on 1 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

harvey-woo cat5th/key-serializer v0.2.5 was discovered to contain a prototype pollution via the function "query". This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

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

## Which versions are affected by CVE-2024-39018?

2 open source packages ship an affected version, including @cat5th/key-serializer.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@cat5th/key-serializer` | npm | All versions to 0.2.5 | None |
| `@cat5th/key-serializer` | npm | All versions to 0.2.5 | None |

## How do I fix CVE-2024-39018?

No fix has been published for CVE-2024-39018 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-39018 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39018 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39018 and fix it if it is affected.

What it is: CVE-2024-39018 is a medium-severity code injection vulnerability in n/a, published on 1 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39018 exists.

Affected packages and fixed versions:
- @cat5th/key-serializer (npm): affected all versions up to 0.2.5; no fix listed
- @cat5th/key-serializer (npm): affected all versions up to 0.2.5; no fix listed

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

## Sources

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

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