Skip to content
Fencer Vulns
medium 5.3

CVE-2018-1107 json

Regular expression deinal of service (ReDoS) in is-my-json-valid

published 2021-03-30 5 y ago modified 2026-06-17 4 mo ago also GHSA-4hpf-3wq7-5rpr , EUVD-2022-0444

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm is-my-json-valid 1.4.1, 2.17.2
  • is-my-json-valid_project is-my-json-valid 1.4.1, 2.17.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1107 updated cvss 5.3

nodejs-is-my-json-valid: ReDoS when validating JSON fields with email format

  • Red Hat Mobile Application Platform 4 nodejs-is-my-json-valid
    affected: no fix available
  • Red Hat Software Collections rh-nodejs6-nodejs-is-my-json-valid
    affected: no fix planned “Will not fix”
  • Red Hat Quay v3 quay/quay-rhel8 v3.6.0-62
    fixed: vendor fix RHSA-2021:3917
  • Red Hat Quay v3 quay/clair-rhel8 v3.6.0-70, quay/quay-builder-rhel8 v3.6.0-44, quay/quay-operator-rhel8 v3.6.0-43, quay/quay-operator-bundle v3.6.0-48, quay/quay-bridge-operator-rhel8 v3.6.0-40, quay/quay-bridge-operator-bundle v3.6.0-35, +3 more Red Hat Enterprise Linux 8 nodejs-is-my-json-valid Red Hat OpenShift Enterprise 3 nodejs-is-my-json-valid
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • snyk.io https://snyk.io/vuln/npm:is-my-json-valid:20180214 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
npm is-my-json-valid
>=2.0.0, <2.17.2
<1.4.1
2.17.2
1.4.1

Affected products

  • n/a nodejs-is-my-json-valid

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.