Skip to content

Command injection vulnerability in @prisma/sdk in getPackedPackage function

High severity GitHub Reviewed Published Mar 31, 2021 in prisma/prisma • Updated Feb 1, 2023

Package

npm @prisma/sdk (npm)

Affected versions

< 2.20.0

Patched versions

2.20.0

Description

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 prisma/prisma#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:

References

@janpio janpio published to prisma/prisma Mar 31, 2021
Reviewed Mar 31, 2021
Published to the GitHub Advisory Database Apr 6, 2021
Published by the National Vulnerability Database Apr 29, 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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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:H/UI:N/S:C/C:H/I:H/A:N

EPSS score

1.185%
(86th percentile)

Weaknesses

CVE ID

CVE-2021-21414

GHSA ID

GHSA-pxcc-hj8w-fmm7

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.