Skip to content
Fencer Vulns
critical 9.8

CVE-2020-17479 json

Validation bypass in jpv

published 2020-08-10 6 y ago modified 2026-06-17 4 mo ago also GHSA-vh6r-g38f-q3w8 , EUVD-2021-1204

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

Summary

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

Patch / fix

  • npm jpv 2.2.2
  • json_pattern_validator_project json_pattern_validator 2.2.2

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/manvel-khnkoyan/jpv/issues/10 referenced PoC, tagged "exploit" by a source, unverified
  • blog.sonatype.com https://blog.sonatype.com/cve-2020-17479 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
npm jpv
<2.2.2
2.2.2

Classification

Weakness
  • CWE-20 Improper Input Validation

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.