CVE-2020-17479: Validation bypass in jpv

jpv Updated 02 Oct 2025

Summary

06/05/2021
Yes i
Critical
9.8

CVE-2020-17479: Validation bypass in jpv. Affects jpv versions < 2.2.2. Fixed in 2.2.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The jpv package is an npm package used for validating JSON patterns. It provides functionality to validate JSON objects against predefined patterns. This vulnerability affects versions prior to 2.2.2 of the jpv package. The package is vulnerable to a validation bypass issue, allowing corrupted arrays to pass the validation process.

Vulnerability Detail

The vulnerability in the jpv package allows for the bypass of input validation. This means that corrupted arrays can pass the validation process without being detected. This can lead to potential security risks as the validation process is meant to ensure the integrity and validity of the input data. Attackers can exploit this vulnerability to inject malicious or unexpected data into the system, potentially leading to further security issues or data corruption.

How To Fix

Minimum fixed version

2.2.2

This is the first release that contains the fix.

npm install jpv@2.2.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update the jpv package to the fixed version to ensure the proper validation of input data.

Conclusion

The jpv package prior to version 2.2.2 is vulnerable to a validation bypass issue. This can allow corrupted arrays to pass the validation process, potentially leading to security risks and data corruption. It is crucial to update the jpv package to version 2.2.2 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for jpv →

Share this vulnerability

FAQ

The vulnerability allows for the bypass of input validation, potentially leading to the injection of malicious or unexpected data into the system.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you if the jpv package version is vulnerable.

There are no known public exploits for this vulnerability at the moment. However, it is crucial to update the jpv package to the fixed version to prevent any potential exploitation.

Manual input validation can help mitigate this vulnerability to some extent. However, it is still recommended to update the jpv package to the fixed version to ensure comprehensive validation and prevent any potential bypass.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide assistance and guidance on fixing the vulnerability in your application.

Related vulnerabilities

Recent vulnerabilities recorded for jpv.

How To Fix

Minimum fixed version

2.2.2

This is the first release that contains the fix.

npm install jpv@2.2.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback