# GHSA-xx4c-jj58-r7x6: Inefficient Regular Expression Complexity in Validator.js

> An attacker can cause a denial of service by exploiting inefficient regular expressions in the validator library's trim functions.

- **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:** 19 Nov 2021

## What is GHSA-xx4c-jj58-r7x6?

GHSA-xx4c-jj58-r7x6 is a denial of service vulnerability in validator, published on 19 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact
Versions of `validator` prior to 13.7.0 are affected by an inefficient Regular Expression complexity  when using the `rtrim` and `trim` sanitizers.

### Patches
The problem has been patched in validator 13.7.0

## Which versions are affected by GHSA-xx4c-jj58-r7x6?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `validator` | npm | From 11.1.0 | 13.7.0 |
| `validator` | npm | From 11.1.0 | 13.7.0 |

## How do I fix GHSA-xx4c-jj58-r7x6?

Upgrade validator to 13.7.0 or later.

## Is GHSA-xx4c-jj58-r7x6 being exploited?

There is no known exploitation of GHSA-xx4c-jj58-r7x6 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-xx4c-jj58-r7x6 and fix it if it is affected.

What it is: GHSA-xx4c-jj58-r7x6 is a denial of service vulnerability in validator, published on 19 Nov 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-xx4c-jj58-r7x6 in the wild and no public exploit code.

Affected packages and fixed versions:
- validator (npm): affected from 11.1.0; fixed in 13.7.0
- validator (npm): affected from 11.1.0; fixed in 13.7.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-xx4c-jj58-r7x6/ (Markdown: https://insights.sbomify.com/GHSA-xx4c-jj58-r7x6/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-xx4c-jj58-r7x6

---
From sbomify Insights: https://insights.sbomify.com/GHSA-xx4c-jj58-r7x6/
Summaries are generated and may contain mistakes; the official description above is the record.