LiveActive security incident?Get immediate response
CVE Record

CVE-2020-17479: jpv (aka Json Pattern Validator) before 2.2.2 does not properly validate input, as demonstrated by a corrup...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-17479 affects the npm package jpv, also called Json Pattern Validator, before version 2.2.2. The package may not correctly validate malformed input, shown by a corrupted array case. Business urgency depends on whether applications rely on jpv to reject unsafe or malformed JSON.

Executive priority

Prioritize as a dependency hygiene and validation integrity issue. It is not supported as actively exploited in the supplied evidence, but teams should upgrade promptly where jpv protects important data flows or accepts external JSON.

Technical view

The CVE record describes improper input validation in jpv before 2.2.2. Public metadata does not provide CVSS, CWE, affected CPEs, or detailed impact. Treat this as a dependency risk in Node.js projects where jpv enforces schema-like controls on untrusted JSON.

Likely exposure

Exposure is most likely in Node.js applications or services that directly or transitively depend on jpv versions before 2.2.2, especially where external JSON is accepted and jpv validation decisions affect security, authorization, persistence, or workflow integrity.

Exploitation context

The supplied sources do not show CISA KEV listing or confirmed active exploitation. They do show a public GitHub issue, a fixing commit, npm package reference, and Sonatype advisory coverage, so the weakness is public but exploitation evidence is incomplete.

Researcher notes

The public record is sparse: no CVSS, CWE, CPE, or detailed exploit conditions are provided in the bundle. Analysis should focus on confirming package presence, version, trust boundary, and whether jpv validation results gate sensitive behavior.

Mitigation direction

  • Upgrade jpv to version 2.2.2 or later where used.
  • Check direct and transitive npm dependencies for jpv before 2.2.2.
  • Review vendor, npm, and Sonatype guidance for any additional remediation notes.
  • Avoid relying solely on jpv for security-critical validation until upgraded.
  • Add defensive validation around untrusted JSON inputs where business impact is high.

Validation and detection

  • Inspect package manifests and lockfiles for jpv version usage.
  • Confirm deployed artifacts do not include jpv before 2.2.2.
  • Identify code paths where jpv validates externally supplied JSON.
  • Regression-test malformed array handling after upgrade.
  • Verify dependency scanning reports no remaining CVE-2020-17479 findings.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-17479 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.