Skip to content

Prototype Pollution in bmoor

High severity GitHub Reviewed Published May 10, 2021 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

npm bmoor (npm)

Affected versions

< 0.8.12

Patched versions

0.8.12

Description

The package bmoor before 0.8.12 are vulnerable to Prototype Pollution via the set function.

References

Published by the National Vulnerability Database Oct 2, 2020
Reviewed Apr 22, 2021
Published to the GitHub Advisory Database May 10, 2021
Last updated Jan 27, 2023

Severity

High

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
Low
Integrity
Low
Availability
Low

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:L/I:L/A:L

EPSS score

0.436%
(75th percentile)

Weaknesses

CVE ID

CVE-2020-7736

GHSA ID

GHSA-h3rx-g5c9-8q4x

Source code

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