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.
CVE-2018-1107 - Medium Severity Vulnerability
Vulnerable Library - is-my-json-valid-2.17.1.tgz
A JSONSchema validator that uses code generation to be extremely fast
Library home page: https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.17.1.tgz
Path to dependency file: /wagtail/package.json
Path to vulnerable library: /node_modules/is-my-json-valid/package.json
Dependency Hierarchy: - eslint-2.13.1.tgz (Root Library) - :x: **is-my-json-valid-2.17.1.tgz** (Vulnerable Library)
Found in base branch: master
Vulnerability Details
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.
Publish Date: 2021-03-30
URL: CVE-2018-1107
CVSS 3 Score Details (5.3)
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-4hpf-3wq7-5rpr
Release Date: 2021-03-30
Fix Resolution (is-my-json-valid): 2.17.2
Direct dependency fix Resolution (eslint): 3.0.0
Step up your Open Source Security Game with Mend here