CVE-2018-1107 is a medium-severity (CVSS 5.3) Uncontrolled Resource Consumption vulnerability in is-my-json-valid. 1 public exploit reference exists, so weaponization risk is real. A fix is available for is-my-json-valid — see the affected versions and patch details below.
Regular expression deinal of service (ReDoS) in is-my-json-valid
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2018-1107 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
is-my-json-validnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | is-my-json-valid | ≥ 2.0.0&&< 2.17.2 | 2.17.2npm install is-my-json-valid@2.17.2 |
| 📦npm | is-my-json-valid | all versions | 1.4.1npm install is-my-json-valid@1.4.1 |
Affected Products
is-my-json-validis-my-json-valid_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for is-my-json-valid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update is-my-json-valid to 2.17.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1107 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
In Red Hat Quay the is-my-json-valid library is included as a build time dependency of protractor. It's only used at build time, not at runtime reducing the impact to low.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Quay 3 | quay/quay-rhel8:v3.6.0-62 | RHSA-2021:3917 |
Frequently Asked Questions
Is CVE-2018-1107 in your dependencies?
Find it across npm, including transitive dependencies.