OS Command Injection in @prisma/sdk (CVE-2021-21414)
Summary
OS command injection in @prisma/sdk (CVE-2021-21414). Confidential information can be exposed externally. Exploitable via getPackedPackage. Mitigation: upgrade to 2.20.0 or later.
Original description
The description as published by the source.
Impact
As of today, we are not aware of any Prisma users or external consumers of the @prisma/sdk package who are affected by this security vulnerability.
This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.
It only affects the getPackedPackage function and this function is not advertised and only used for tests & building our CLI, no malicious code was found after checking our codebase.
Patches
Fixed in
- @prisma/sdk@2.20.0 (latest channel)
- @prisma/sdk@2.20.0-dev.29 (dev channel)
Pull Request closing this vulnerability https://github.com/prisma/prisma/pull/6245
Acknowledgements
This issue was discovered and reported by GitHub Engineer @erik-krogh (Erik Krogh Kristensen).
For more information
If you have any questions or comments about this advisory:
- Create a discussion in the Prisma repository
- Email us at security@prisma.io
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-21414 has been found in @prisma/sdk.
Attackers can target a specific entry point like getPackedPackage over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade @prisma/sdk to 2.20.0 or later.
If unsure, ask your IT team or search "@prisma/sdk CVE-2021-21414" on the vendor's site.
CVE-2021-21414 (@prisma/sdk) — CWE-78
Attack vector: remote (network-reachable) / no user interaction
Attack surface: getPackedPackage
Patched: 2.20.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in @prisma/sdk. Attackers reach the vulnerable code path via getPackedPackage.
Check the vendor advisory for the affected versions of @prisma/sdk. Attack surface: getPackedPackage.
Severity: ?. Confidential information can be exposed externally.
Update to 2.20.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@prisma/sdk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@prisma/sdk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@prisma/sdkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @prisma/sdk to 2.20.0ステージング環境で 2.20.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web security.netapp.com