Quick answers
- Is CVE-2021-21414 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2021-21414 being exploited in the wild.
- How severe is CVE-2021-21414?
- Low severity, with a CVSS score of 3.1, published 6 April 2021.
- Which products and versions are affected?
- @prisma/sdk (npm) SEMVER:introduced=0,fixed=2.20.0.
- Is there a fix for CVE-2021-21414?
- Yes. @prisma/sdk (npm): upgrade to 2.20.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2021-21414 attacked?
- It is attacked over the network.
- Am I affected by CVE-2021-21414?
- Check whether you run @prisma/sdk (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
- @prisma/sdk (npm): upgrade to 2.20.0 or later
npm install @prisma/sdk@2.20.0
Technical details
A command injection vulnerability (CWE-78) exists in the @prisma/sdk getPackedPackage function, where untrusted input is not properly sanitized before being passed to shell commands. The vulnerability requires that a client library calls the vulnerable method with untrusted input; the attack vector is network-based if the SDK is exposed through a web service or similar. An attacker can inject shell metacharacters to execute arbitrary commands with the privileges of the process running the SDK. The vulnerability has been fixed in @prisma/sdk version 2.20.0 and later.
Affected products
- Prisma SDK before 2.20.0
Identifiers
- CVE-2021-21414
- GHSA-pxcc-hj8w-fmm7
Timeline
- 2021-03-31: disclosed
- 2021-04-06: patched: Fixed in @prisma/sdk@2.20.0