# GHSA-65p8-3hm4-h9h8: Denial of Service in rgb2hex

> Attackers can cause denial of service in applications using rgb2hex by submitting specially crafted invalid color values.

- **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:** 23 Aug 2019

## What is GHSA-65p8-3hm4-h9h8?

GHSA-65p8-3hm4-h9h8 is a denial of service vulnerability in rgb2hex, published on 23 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `rgb2hex` are vulnerable to Regular Expression Denial of Service (ReDoS) when an attacker can pass in a specially crafted invalid color value.

## Recommendation

Update to version 0.1.6 or later.

## Which versions are affected by GHSA-65p8-3hm4-h9h8?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rgb2hex` | npm | All versions | 0.1.6 |
| `rgb2hex` | npm | All versions | 0.1.6 |

## How do I fix GHSA-65p8-3hm4-h9h8?

Upgrade rgb2hex to 0.1.6 or later.

## Is GHSA-65p8-3hm4-h9h8 being exploited?

There is no known exploitation of GHSA-65p8-3hm4-h9h8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-65p8-3hm4-h9h8 and fix it if it is affected.

What it is: GHSA-65p8-3hm4-h9h8 is a denial of service vulnerability in rgb2hex, published on 23 Aug 2019. 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-65p8-3hm4-h9h8 in the wild and no public exploit code.

Affected packages and fixed versions:
- rgb2hex (npm): affected all versions; fixed in 0.1.6
- rgb2hex (npm): affected all versions; fixed in 0.1.6

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-65p8-3hm4-h9h8/ (Markdown: https://insights.sbomify.com/GHSA-65p8-3hm4-h9h8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-65p8-3hm4-h9h8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-65p8-3hm4-h9h8/
Summaries are generated and may contain mistakes; the official description above is the record.