Skip to content

Arbitrary Code Execution in grunt

High severity GitHub Reviewed Published May 6, 2021 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

npm grunt (npm)

Affected versions

< 1.3.0

Patched versions

1.3.0

Description

The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.

References

Published by the National Vulnerability Database Sep 3, 2020
Reviewed May 4, 2021
Published to the GitHub Advisory Database May 6, 2021
Last updated Feb 1, 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
High
Privileges required
Low
User interaction
Required
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:H/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.851%
(83rd percentile)

Weaknesses

CVE ID

CVE-2020-7729

GHSA ID

GHSA-m5pj-vjjf-4m3h

Source code

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