# GHSA-w5q7-3pr9-x44w: Denial of Service in serialize-to-js

> Attackers can cause indefinite loops and denial of service by providing unvalidated input to the serialize-to-js library.

- **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:** 2 Sep 2020

## What is GHSA-w5q7-3pr9-x44w?

GHSA-w5q7-3pr9-x44w is a denial of service vulnerability in serialize-to-js, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `serialize-to-js` prior to 2.0.0 are vulnerable to Denial of Service. User input is not properly validated, allowing attackers to provide inputs that lead the execution to loop indefinitely.

## Recommendation

Upgrade to version 2.0.0 or later.

## Which versions are affected by GHSA-w5q7-3pr9-x44w?

2 open source packages ship an affected version, including serialize-to-js.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `serialize-to-js` | npm | All versions | 2.0.0 |
| `serialize-to-js` | npm | All versions | 2.0.0 |

## How do I fix GHSA-w5q7-3pr9-x44w?

Upgrade serialize-to-js to 2.0.0 or later.

## Is GHSA-w5q7-3pr9-x44w being exploited?

There is no known exploitation of GHSA-w5q7-3pr9-x44w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-w5q7-3pr9-x44w and fix it if it is affected.

What it is: GHSA-w5q7-3pr9-x44w is a denial of service vulnerability in serialize-to-js, published on 2 Sep 2020. 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-w5q7-3pr9-x44w in the wild and no public exploit code.

Affected packages and fixed versions:
- serialize-to-js (npm): affected all versions; fixed in 2.0.0
- serialize-to-js (npm): affected all versions; fixed in 2.0.0

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-w5q7-3pr9-x44w/ (Markdown: https://insights.sbomify.com/GHSA-w5q7-3pr9-x44w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-w5q7-3pr9-x44w

---
From sbomify Insights: https://insights.sbomify.com/GHSA-w5q7-3pr9-x44w/
Summaries are generated and may contain mistakes; the official description above is the record.