Skip to content

safe-eval vulnerable to Prototype Pollution via the safeEval function

Critical severity GitHub Reviewed Published Apr 11, 2023 to the GitHub Advisory Database • Updated Apr 14, 2023

Package

npm safe-eval (npm)

Affected versions

<= 0.4.2

Patched versions

None

Description

All versions of the package safe-eval are vulnerable to Prototype Pollution via the safeEval function, due to improper sanitization of its parameter content.

References

Published by the National Vulnerability Database Apr 11, 2023
Published to the GitHub Advisory Database Apr 11, 2023
Reviewed Apr 11, 2023
Last updated Apr 14, 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
Changed
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:C/C:H/I:H/A:H

EPSS score

0.183%
(57th percentile)

Weaknesses

CVE ID

CVE-2023-26121

GHSA ID

GHSA-hcg3-56jf-x4vh

Source code

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