# CVE-2018-1107: Regular expression deinal of service (ReDoS) in is-my-json-valid

> An attacker can cause excessive CPU consumption and denial of service by submitting specially crafted JSON data to applications using this validation library.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2021
- **Updated:** 5 Aug 2024
- **Also known as:** CLSA-2026-1792476292, GHSA-4hpf-3wq7-5rpr

## What is CVE-2018-1107?

CVE-2018-1107 is a medium-severity denial of service vulnerability in nodejs-is-my-json-valid, published on 30 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU time when validated.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2018-1107?

4 open source packages ship an affected version, including is-my-json-valid. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `is-my-json-valid` | npm | All versions | 1.4.1 |
| `is-my-json-valid` | npm | All versions | 1.4.1 |
| `is-my-json-valid` | npm | From 2.0.0 | 2.17.2 |
| `is-my-json-valid` | npm | From 2.0.0 | 2.17.2 |

Products: Is-My-Json-Valid Project Is-My-Json-Valid.

## How do I fix CVE-2018-1107?

Upgrade is-my-json-valid to a fixed version for your release line: 1.4.1 or 2.17.2.

## Is CVE-2018-1107 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1107 and fix it if it is affected.

What it is: CVE-2018-1107 is a medium-severity denial of service vulnerability in nodejs-is-my-json-valid, published on 30 Mar 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 CVE-2018-1107 in the wild and no public exploit code.

Affected packages and fixed versions:
- is-my-json-valid (npm): affected all versions; fixed in 1.4.1
- is-my-json-valid (npm): affected all versions; fixed in 1.4.1
- is-my-json-valid (npm): affected from 2.0.0; fixed in 2.17.2
- is-my-json-valid (npm): affected from 2.0.0; fixed in 2.17.2

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-2018-1107/ (Markdown: https://insights.sbomify.com/CVE-2018-1107/index.md)
```

## Sources

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

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