Skip to content

Missing Handler in @scandipwa/magento-scripts

Moderate severity GitHub Reviewed Published Jun 14, 2021 in scandipwa/create-magento-app • Updated Feb 1, 2023

Package

npm @scandipwa/magento-scripts (npm)

Affected versions

>= 1.5.1, < 1.5.3

Patched versions

1.5.3

Description

Impact

After changing the function from synchronous to asynchronous there wasn't implemented handler in the start, stop, exec and logs commands, effectively making them unusable.

Patches

Version 1.5.3 contains patches for the problems described above.

Workarounds

Upgrade to patched or latest (recommended) version npm i @scandipwa/magento-scripts@1.5.3 or npm i @scandipwa/magento-scripts@latest.

References

New releases always available here: https://github.com/scandipwa/create-magento-app/releases

For more information

If you have any questions or comments about this advisory:

References

@ejnshtein ejnshtein published to scandipwa/create-magento-app Jun 14, 2021
Published by the National Vulnerability Database Jun 14, 2021
Reviewed Jun 16, 2021
Published to the GitHub Advisory Database Jun 21, 2021
Last updated Feb 1, 2023

Severity

Moderate

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
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
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:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2021-32684

GHSA ID

GHSA-52qp-gwwh-qrg4

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.