Skip to content

Validation bypass in jpv

Critical severity GitHub Reviewed Published May 6, 2021 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

npm jpv (npm)

Affected versions

< 2.2.2

Patched versions

2.2.2

Description

jpv (aka Json Pattern Validator) before 2.2.2 does not properly validate input, as demonstrated by a corrupted array.

References

Published by the National Vulnerability Database Aug 10, 2020
Reviewed May 5, 2021
Published to the GitHub Advisory Database May 6, 2021
Last updated Feb 1, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.667%
(80th percentile)

Weaknesses

CVE ID

CVE-2020-17479

GHSA ID

GHSA-vh6r-g38f-q3w8

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.