# CVE-2023-39619: Inefficient Regular Expression Complexity in node-email-check

> An attacker can cause a denial of service in the Node Email Check library by sending a crafted string to the scpSyntax component.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2023
- **Updated:** 11 Sep 2024
- **Also known as:** GHSA-9242-6p36-6256

## What is CVE-2023-39619?

CVE-2023-39619 is a high-severity denial of service vulnerability in n/a, published on 24 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ReDos in NPMJS Node Email Check v.1.0.4 allows an attacker to cause a denial of service via a crafted string to the scpSyntax component.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2023-39619?

2 open source packages ship an affected version, including node-email-check. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-email-check` | npm | All versions to 1.0.4 | None |
| `node-email-check` | npm | All versions to 1.0.4 | None |

Products: Teomantuncer Node Email Check.

## How do I fix CVE-2023-39619?

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

## Is CVE-2023-39619 being exploited?

There is no known exploitation of CVE-2023-39619 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-39619 and fix it if it is affected.

What it is: CVE-2023-39619 is a high-severity denial of service vulnerability in n/a, published on 24 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-39619 in the wild and no public exploit code.

Affected packages and fixed versions:
- node-email-check (npm): affected all versions up to 1.0.4; no fix listed
- node-email-check (npm): affected all versions up to 1.0.4; 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-2023-39619/ (Markdown: https://insights.sbomify.com/CVE-2023-39619/index.md)
```

## Sources

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

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