Skip to content

Validation Bypass in schema-inspector

Critical severity GitHub Reviewed Published Jun 10, 2020 to the GitHub Advisory Database • Updated Jan 9, 2023

Package

npm schema-inspector (npm)

Affected versions

< 1.6.9

Patched versions

1.6.9

Description

In schema-inspector before 1.6.9, a maliciously crafted JavaScript object can bypass the sanitize() and the validate() function used within schema-inspector.

References

Reviewed Jun 10, 2020
Published to the GitHub Advisory Database Jun 10, 2020
Last updated Jan 9, 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.235%
(62nd percentile)

Weaknesses

CVE ID

CVE-2019-10781

GHSA ID

GHSA-r24h-634p-m72x

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.