CVE-2018-1107 — It was discovered that the is-my-json-valid JavaScript library used an inefficie

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.

01What is this vulnerability?

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.

02Affected products

Vendor	Product	Versions
n	a / nodejs	is-my-json-valid — is-myjson-valid 2.17.2, is-myjson-valid 1.4.1

03Active exploitation status

Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.

04Recommended remediation

• Patch to a fixed version listed in the vendor advisory (see references below).
• Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
• Hunt historical logs for exploitation indicators — see Detection signatures below.

05Technical details

For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.

06Detection signatures

Ask SARA in chat to draft a starting detection for this CVE in your stack of choice.

07Related CVEs

No directly-cited follow-up CVEs in the KB record for this advisory. The references list in section 09 carries the vendor cross-references.

08Timeline

• Published: 2021-03-30T01:48:27.000Z
• Last modified: 2024-08-05T03:51:48.538Z

09References

• bugzilla.redhat.com — https://bugzilla.redhat.com/show_bug.cgi?id=1546357
• snyk.io — https://snyk.io/vuln/npm:is-my-json-valid:20180214