Skip to content

mockery is vulnerable to prototype pollution

Critical severity GitHub Reviewed Published Oct 12, 2022 to the GitHub Advisory Database • Updated Jul 28, 2023

Package

npm mockery (npm)

Affected versions

<= 2.1.0

Patched versions

None

Description

Prototype pollution vulnerability in function enable in mockery.js in mfncooper mockery commit 822f0566fd6d72af8c943ae5ca2aa92e516aa2cf via the key variable in mockery.js.

References

Published by the National Vulnerability Database Oct 12, 2022
Published to the GitHub Advisory Database Oct 12, 2022
Reviewed Jul 28, 2023
Last updated Jul 28, 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.240%
(63rd percentile)

Weaknesses

CVE ID

CVE-2022-37614

GHSA ID

GHSA-gmwp-3pwc-3j3g

Source code

Credits

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