Skip to content

Blackprint @blackprint/engine Prototype Pollution issue

Critical severity GitHub Reviewed Published May 20, 2024 to the GitHub Advisory Database • Updated Jul 5, 2024

Package

npm @blackprint/engine (npm)

Affected versions

>= 0.8.12, < 0.9.2

Patched versions

0.9.2

Description

A Prototype Pollution issue in Blackprint @blackprint/engine 0.8.12 through 0.9.1 allows an attacker to execute arbitrary code via the _utils.setDeepProperty function of engine.min.js.

References

Published by the National Vulnerability Database May 20, 2024
Published to the GitHub Advisory Database May 20, 2024
Reviewed May 20, 2024
Last updated Jul 5, 2024

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

Weaknesses

CVE ID

CVE-2024-24294

GHSA ID

GHSA-g3q2-vcjq-rgrc

Source code

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