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.
The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Grunt | Gruntjs | * | 1.3.0 (excluding) |
| Grunt | Ubuntu | bionic | * |
| Grunt | Ubuntu | esm-apps/focal | * |
| Grunt | Ubuntu | focal | * |
| Grunt | Ubuntu | groovy | * |
| Grunt | Ubuntu | trusty | * |
| Grunt | Ubuntu | upstream | * |
Developers often choose default values that leave the product as open and easy to use as possible out-of-the-box, under the assumption that the administrator can (or should) change the default value. However, this ease-of-use comes at a cost when the default is insecure and the administrator does not change it.