Quick answers
- Is CVE-2022-0436 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-0436 being exploited in the wild.
- How severe is CVE-2022-0436?
- Low severity, with a CVSS score of 3.1, published 13 April 2022.
- Which products and versions are affected?
- grunt (npm) SEMVER:introduced=0,fixed=1.5.2.
- Is there a fix for CVE-2022-0436?
- Yes. grunt (npm): upgrade to 1.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-0436 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2022-0436?
- Check whether you run grunt (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- grunt (npm): upgrade to 1.5.2 or later
npm install grunt@1.5.2
Technical details
Grunt prior to version 1.5.2 is vulnerable to path traversal (CWE-22) via improper link handling. The vulnerability exists in how Grunt processes file paths, allowing directory traversal sequences such as "../" to escape intended directory boundaries. The attack requires local access and limited user privileges to execute. An attacker can achieve arbitrary file read access with the privileges of the Grunt process, potentially exposing sensitive configuration files, private keys, or source code. The vulnerability was patched in Grunt version 1.5.2, with fixes merged in PR #1743.
Affected products
- Grunt Grunt prior to 1.5.2
Identifiers
- CVE-2022-0436
- GHSA-j383-35pm-c5h4
Timeline
- 2022-04-13: disclosed
- 2022-04-12: patched: Fixed in version 1.5.2