# GHSA-36jr-mh4h-2g58: d3-color vulnerable to ReDoS

> An attacker can cause a denial of service in applications using the d3-color library by triggering a Regular expression Denial of Service.

- **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:** 29 Sep 2022

## What is GHSA-36jr-mh4h-2g58?

GHSA-36jr-mh4h-2g58 is a denial of service vulnerability in d3-color, published on 29 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The d3-color module provides representations for various color spaces in the browser. Versions prior to 3.1.0 are vulnerable to a Regular expression Denial of Service. This issue has been patched in version 3.1.0. There are no known workarounds.

## Which versions are affected by GHSA-36jr-mh4h-2g58?

2 open source packages ship an affected version, including d3-color.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `d3-color` | npm | From 1.0.2 | 3.1.0 |
| `d3-color` | npm | From 1.0.2 | 3.1.0 |

## How do I fix GHSA-36jr-mh4h-2g58?

Upgrade d3-color to 3.1.0 or later.

## Is GHSA-36jr-mh4h-2g58 being exploited?

There is no known exploitation of GHSA-36jr-mh4h-2g58 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-36jr-mh4h-2g58 and fix it if it is affected.

What it is: GHSA-36jr-mh4h-2g58 is a denial of service vulnerability in d3-color, published on 29 Sep 2022. 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-36jr-mh4h-2g58 in the wild and no public exploit code.

Affected packages and fixed versions:
- d3-color (npm): affected from 1.0.2; fixed in 3.1.0
- d3-color (npm): affected from 1.0.2; fixed in 3.1.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-36jr-mh4h-2g58/ (Markdown: https://insights.sbomify.com/GHSA-36jr-mh4h-2g58/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-36jr-mh4h-2g58

---
From sbomify Insights: https://insights.sbomify.com/GHSA-36jr-mh4h-2g58/
Summaries are generated and may contain mistakes; the official description above is the record.